Duplicate Grabs

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

No annotations present, so description carries full burden. It only states the basic purpose, omitting any behavioral traits such as whether it's read-only, destructive, requires specific permissions, pagination behavior, or output format. This is insufficient for a tool with 11 parameters.

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 extremely brief (one sentence) but lacks structure and critical information. It is under-specified rather than efficiently concise, sacrificing completeness for brevity.

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?

With 11 parameters, 0% schema description coverage, no output schema, and no annotations, the description fails to provide adequate context. The agent has no understanding of filtering, pagination, detail levels, or field selection. Severely incomplete.

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 does not explain any parameter meaning. It mentions 'download id or title' but these are not actual parameter names. The 11 parameters (to, app, from, page, etc.) are left completely unexplained.

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 'Find' and the resource 'repeated grabs' with specific criteria (same download id or title). This distinguishes it from sibling tools like 'get_grab_history' or 'download_volume_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 like 'get_grab_history' or 'continuing_query'. No mention of prerequisites, exclusions, or context for effective use.

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