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

With no annotations provided, the description carries the full burden. It discloses the destructive nature and the token requirement, and it calls out that output files are also deleted. However, it stops short of stating irreversibility, partial-failure behavior, or what happens if the request does not exist.

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 two short sentences plus an Args block. The core behavior is front-loaded, every sentence earns its place, and there is no filler or redundant restating of the schema.

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 low-complexity, single-parameter destructive tool, the description covers purpose, target resource, auth requirement, and the effect on output files. An output schema exists, so return-value details are unnecessary. Only a note on irreversibility would round it out.

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%, so the description must compensate. It does: 'rindex: Request index/ID to purge' gives meaning beyond the bare schema type/title, clarifying that the parameter identifies the request to delete. For a single simple parameter this is sufficient.

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 opens with a specific verb and resource: 'Delete a subsetting request and its output files.' It clearly distinguishes this destructive tool from the many get_* and submit_* siblings, and the single parameter is named and explained.

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 tool's purpose as a deletion/cleanup operation makes its usage context clear, and it explicitly requires GDEX_TOKEN as a prerequisite. It does not name alternative tools or exclusions, but none are needed given the unambiguous destructive scope.

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