delete_indexer_bulk

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

Annotations already provide destructiveHint=true and idempotentHint=true, so 'Delete Indexer' is consistent. The description adds a note about reading the schema before constructing the body, which gives some context, but it does not disclose side effects, scope of deletion, or response behavior beyond what annotations imply.

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 compact and front-loaded with the action. The endpoint and Args sections are clearly structured, though the endpoint line is somewhat redundant with the tool name and the pointer to GET/schema could be more concise.

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 is incomplete: it does not state what the request body must contain to identify indexers, any limits, or what the output schema represents. The pointer to the schema endpoint shifts the burden to the agent and does not make the tool self-sufficient.

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, the description must compensate. It identifies 'body' as a request payload and directs the agent to the GET or /schema endpoint for field details, which is a useful pointer. However, it does not specify how to express which indexers are deleted (e.g., list of IDs), leaving the payload semantics underspecified.

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 a specific verb and resource ('Delete Indexer'), and the endpoint URL adds bulk context. However, it does not explicitly differentiate from delete_indexer_by_id or describe the bulk nature beyond the tool name and endpoint, so it lacks clear sibling differentiation.

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?

There is no guidance on when to use this bulk endpoint versus single-delete alternatives like delete_indexer_by_id. The only advice, to read the GET or /schema endpoint first, is about constructing the request body, not about tool selection.

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