upload_asset

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations, so description carries full burden. Discloses proxy behavior, sandboxing binding, async pipeline triggering, pending state, and recommendation for retrieval. Comprehensive for a simple upload tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

Moderately sized but every sentence earns its place. Logical flow: purpose, proxy details, sandboxing, pipeline, state, recommendation. Slightly verbose but not wasteful.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no annotations or output schema, description covers all necessary aspects: input, process, side effects, state transitions, and next steps. Sufficient for correct invocation and expectation management.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline 3. Description adds value: filePath example format and absolute path hint, filename default behavior. Enhances schema without repeating.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

Describes a specific action (upload) and resource (local file to Picsha AI platform) with clear scope (directly, via proxy). Differentiates from siblings like trigger_url_ingest which handles URL ingestion.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states when to use: uploading local files. Mentions sandboxing binding and async pipeline, implying post-upload step (use get_asset). Does not explicitly list when not to use or alternatives, but context is clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.