Get Indexers

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

With no annotations and a bare description, the tool's behavioral traits are not disclosed. The description omits critical details such as pagination behavior, required parameters beyond 'app', or any side effects. The agent cannot infer safety or performance characteristics.

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?

At only two words, the description is extremely terse. While concise is good, this brevity sacrifices necessary detail for a tool with 11 parameters. It is under-specified rather than efficiently informative.

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), the description is woefully incomplete. It fails to describe pagination, filtering, field selection, or any grouping behavior, making it nearly impossible for an agent to use the tool correctly without prior knowledge.

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 parameters. While the schema provides types and enums for 'app' and 'detail', the semantics of 'to', 'from', 'cursor', etc., are unexplained, leaving the agent to guess their purpose.

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 'List indexers' clearly states the verb and resource, making the basic purpose understandable. However, it does not differentiate from the sibling tool 'get_indexer' which likely retrieves a single indexer, leaving ambiguity about scope.

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 is provided on when to use this tool versus alternatives like 'get_indexer' or other related tools. The agent receives no context about prerequisites or typical use cases.

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