download_filled_form

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

With no annotations provided, the description carries full burden for disclosing behavior. It fails to mention that the tool can delete the form after download (via 'delete_after_read' parameter), or that it supports preview mode and size limits. This is a significant gap for a tool with potentially destructive side effects.

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 short sentence, which is under-specified for a tool with 4 parameters and complex behavior. It achieves conciseness at the expense of essential information, making it insufficiently 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?

Given the tool's complexity (4 parameters, no param descriptions) and lack of annotations, the description is incomplete. It does not cover important aspects like return format, side effects, or parameter roles. The existence of an output schema does not compensate for missing behavioral context.

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?

The input schema has 4 parameters with 0% description coverage, and the description does not explain any parameter. The description adds no value beyond the schema itself, leaving the agent without understanding what 'only_preview', 'delete_after_read', or 'ignore_size_limit' do.

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 'Retrieve a filled PDF form' uses a specific verb ('retrieve') and clearly identifies the resource ('filled PDF form'). It effectively distinguishes the tool from siblings like 'delete_filled_form' and 'analyze_form_for_filling', which have different 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 no guidance on when to use this tool versus alternatives. It does not mention prerequisites (e.g., form must already be filled) or specify use cases, leaving the agent to infer context.

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