delete_indexer_bulk

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

Annotations already provide destructiveHint=true and idempotentHint=true, and the description does not contradict them. It adds a useful preflight instruction ('Read the matching GET or the /schema endpoint first'), though it does not describe the actual destructive effects or response behavior.

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 tight and front-loaded with the action, endpoint, and argument guidance. There is no filler, though the bulk semantics could have been made explicit in prose.

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?

For a destructive bulk operation, the description omits what the body should contain to select targets and does not say 'multiple' or 'bulk' in prose. It relies heavily on annotations and external schema references, leaving the agent to infer critical invocation details.

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 only labels 'body' as 'Request payload' before pointing to external endpoints. It does not describe expected fields or shapes, though the pointer to the schema endpoint provides an actionable discovery path.

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 uses a clear verb and resource ('Delete Indexer') and includes the endpoint '/api/v1/indexer/bulk', which signals the bulk variant and distinguishes it from delete_indexer_by_id. It is brief though not explicitly phrased as 'delete multiple indexers,' relying on tool name and endpoint.

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 given on when to use this bulk delete versus the single delete alternative, and no exclusions or alternative tool names are mentioned. The only instruction is to consult the GET/schema endpoint, which addresses payload preparation rather than tool selection.

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