add_asset_version

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

Without annotations, the description discloses the two-step process: returns a signed S3 URL, then PUT the file there to complete. It also notes it initiates a new version, which is a meaningful side effect. Missing permission requirements or failure behavior, but the core flow is well covered.

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?

Two sentences, front-loaded with the primary action, and every word adds value. No fluff or repetition.

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 moderate complexity, no output schema, and no annotations, the description covers the key flow (initiate, signed URL, PUT) and provides an alternative. It lacks param details but is otherwise complete for an agent to invoke it correctly.

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 only 25% (only id has a description). The description does not explain filename, content_type, or file_size beyond their names, nor clarify how they relate to the upload. With low schema coverage, the description should compensate, but it doesn't.

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?

The description clearly states the action: 'Initiate an upload of a NEW version of an existing asset.' This specifies the verb (initiate upload), resource (asset version), and differentiates from siblings like `upload_file` by focusing on creating a new version rather than a full upload.

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?

Explicit guidance is provided: 'For end-to-end uploads from disk, prefer `upload_file` with the asset id.' This tells the agent exactly when to use this tool versus an alternative, and implies this tool is for staged uploads via signed URL.

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