tokportal_upload_image

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

The description discloses important behavioral traits: it returns a short-lived signed URL, the response contains a secret not stored in the replay ledger, and it explains why Idempotency-Key is rejected. This adds value beyond the annotations, which already indicate non-idempotent and non-read-only behavior.

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?

The description is concise at five sentences and front-loads the purpose in the first sentence. It could be slightly more efficient by combining the idempotency warnings into a single sentence, but it remains clear and well-structured.

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?

The description explains the return value and a key behavioral constraint, but it lacks context on how to use the returned URL, the effect of the 'purpose' parameter, and the overall workflow. Given the nested input schema and the presence of related sibling tools, this leaves some gaps for an AI agent.

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 description coverage is 100%, so the schema already documents the parameters. The description adds no additional meaning to the parameters (filename, bundle_id, content_type, purpose), so it meets the baseline but does not improve understanding.

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 verb and resource: 'Create an image upload URL' and mentions the return value. However, it does not differentiate itself from siblings like tokportal_upload_image_direct or tokportal_upload_image_from_url, which have similar names and purposes.

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?

The description provides a specific 'do not' guideline about Idempotency-Key but offers no guidance on when to use this tool over alternatives. There is no mention of prerequisites, typical use cases, or when to choose this tool over related upload tools.

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