delete_indexer_by_id

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safe-to-delete behavior is covered elsewhere. The description adds no additional behavioral context such as permanence, side effects, authorization requirements, or behavior for nonexistent ids.

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 highly concise: a one-line purpose, the raw endpoint, and a short parameter note. Every component earns its place and the core action is front-loaded with no filler.

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 single-parameter destructive delete with an output schema and annotations covering idempotency and destructiveness, the description is nearly complete. It lacks only explicit usage guidance around alternatives, but the endpoint and schema are sufficient for correct invocation.

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?

The schema documents only 'id' as a required integer, and the description adds that it is a path parameter, which is meaningful. However, the description does not clarify what the id identifies beyond the endpoint path, leaving the parameter semantics mostly self-evident.

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 the action directly as 'Delete Indexer' and includes the HTTP endpoint DELETE /api/v1/indexer/{id}, which identifies the resource and the path parameter. It is clear enough to distinguish from sibling tools like delete_indexer_bulk, though it relies somewhat on the name and endpoint rather than describing the precise 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?

The description gives no guidance on when to use this tool versus alternatives such as delete_indexer_bulk or update_indexer_by_id. It implies singular deletion via the {id} path parameter, but provides no explicit context, prerequisites, or exclusions.

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