Imports By Indexer

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

With no annotations, the description must disclose behavioral traits. It mentions 'count' implying aggregation, but lacks details on pagination, filtering, ordering, or the format of the result. The behavioral profile is largely unspecified.

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?

While short, the description is under-specified. It is missing essential context that would help an agent use the tool correctly, making it too concise to be useful.

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 11 parameters, no output schema, and no annotations, the description is grossly incomplete. It does not explain what constitutes an 'import event', how grouping works, or what the output structure looks like. It fails to provide a complete picture for proper tool usage.

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 coverage is 0%, so the description must compensate by explaining parameters. It does not mention any of the 11 parameters (e.g., 'to', 'from', 'app', 'groupBy'), leaving their meaning entirely to the schema property names, which are insufficient for some parameters like 'cursor' or 'detail'.

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 tool counts import events by indexer, indicating a specific verb and resource. However, it does not differentiate from sibling tools like 'grabs_by_indexer' or 'failed_downloads_by_indexer', which also group 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?

The description provides no guidance on when to use this tool vs. alternatives, such as other 'by_indexer' tools or raw history queries. There is no mention of prerequisites, exclusions, or appropriate contexts.

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