Wasted Downloads

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

No annotations are provided, so the description must fully disclose behavioral traits. It only says 'Estimate', implying it's not an exact count and is likely read-only, but it does not confirm safety, state whether it modifies data, or explain how estimates are computed.

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 too short—one sentence with minimal information. It sacrifices necessary detail for brevity, leading to under-specification.

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 complexity (11 params, no output schema, no annotations), the description is severely incomplete. It fails to explain return values, pagination, filtering options, or how to use the tool effectively.

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 adds no meaning to any of the 11 parameters. The agent gets no help understanding parameters like 'to', 'app', 'cursor', 'detail', 'fields', etc.

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 states it estimates failed or non-imported grab volume, which is clear and aligned with the tool name. However, it could be more specific about what 'volume' means (count/size) and how it distinguishes from similar sibling tools like failed_downloads_by_indexer.

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?

No guidance on when to use this tool versus alternatives. The description is too brief to help the agent choose between wasted_downloads and sibling tools like duplicate_grabs or failed_downloads_by_indexer.

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