Apparently it's possible but not at all straightforward...
See here: https://groups.google.com/forum/#!topic/audiokit/rMxXW8V9fgE
And according to this blog post it's definitely on his radar: http://audiokit.io/blog/2014/12/31/happy-new-year/
There's a large github repo of csound instruments at /ReneNyffenegger/csound-instruments.
Also, a few things at www.csounds.com/mikelson/
Here's my vague take on your questions:
Numeric accuracy of Csound depends on what version you're running -- assuming you're using Csound compiled to use doubles (run csound at the command line and it'll tell you right beside the version number), it should have 15–17 significant decimal digits precision according to wikipedia. So I can't answer your question exactly, but you should have minimum 15 decimal digits available.
Maximum score time is probably only limited to disk-space and/or OS file-size limitations if you're writing a file. Minimum instrument time is likewise open-ended, although anything shorter than 30ms is going to be accoustically meaningless, unless you're working with granular synthesis.
Amplitude is one of the more challenging parts of Csound. Amplitude values are ultimately correlated to the sample format you're working with, making it somewhat convoluted. I'd recommend reading the section on Amplitude from the Csound Book and also looking up the 0dbfs opcode which explains the old technique of working with amplitude and the "newer" method utilizing this opcode.
Ok, maybe not exactly as detailed answers as you were looking for, but that's all I've got.
I used the Csound API a few years ago to build Ethersurface. I can't speak to using the Csound Android app on the store, but I would say using Csound in any way on an Android device is a great deal different from running it on something like a netbook. If you wish to practice csound, definitely use the netbook...