resemble_secure_upload

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

With no annotations, the description carries the full burden. It usefully discloses that the token is short-lived (1 hour) and that the media is private, but it omits other important behaviors like authentication requirements, file size/type limits, upload side effects, and failure handling.

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 a single, efficient sentence that front-loads the action and result. Every phrase adds value with no filler 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?

Although an output schema exists and the description mentions the media_token, this is a mutation tool with no annotations. The description does not cover operational requirements like authentication, file access, size limits, or error conditions, and it leaves the lone parameter under-explained.

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 0% and the description never mentions file_path, which is the only required parameter. It leaves the agent without guidance on what the path should reference, what formats are supported, or how the file is resolved.

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 uses a specific verb ('Upload'), a resource ('private media to Resemble'), and an outcome ('return a short-lived media_token (1 hour) for Detect'). This clearly differentiates it from all sibling tools, which are about detection queries, investigations, and account details, not media 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?

The phrase 'for Detect' implies this tool is a precursor to using detection tools, but the description does not explicitly say when to use it vs alternatives, nor does it name exclusions or alternative tools. It provides context but no direct routing guidance.

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