Failed Downloads By Indexer

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

No annotations are provided, so the description must disclose behavioral traits. It only says 'count failed downloads by indexer', omitting that the tool likely returns aggregated data, uses pagination, or is read-only. No side effects or limitations mentioned.

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?

Extremely concise at 3 words, but severely under-specified for 11 parameters and no annotations. Concision is not valuable when it sacrifices essential information.

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 (11 parameters, no output schema, no annotations) and many siblings, the description is completely inadequate. The agent cannot determine how to invoke the tool correctly or interpret results.

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?

With 0% schema description coverage for 11 parameters, the description adds no parameter explanations. The phrase 'by indexer' hints at grouping but does not correspond to any explicit parameter (e.g., 'groupBy' or 'indexer'). The agent is left guessing parameter meanings.

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 the tool counts failed downloads by indexer, which is a specific verb and resource. However, it does not differentiate from closely related sibling tools like 'failed_history' or 'report_failed_downloads', so it loses a point.

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 like 'failed_history' or 'success_rate_by_indexer'. No context on prerequisites or cases where the tool is inappropriate.

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