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

The description adds the crucial behavioral detail of cascade-deleting all assignments on existing cases, which goes beyond the annotation's destructiveHint. It transparently communicates this side effect, though it doesn't mention idempotency or irreversibility explicitly (though annotations cover these).

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 a single, concise sentence that front-loads the action and includes the essential cascade detail. It is efficient and well-structured.

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 delete operation, the description provides sufficient context: what is deleted and the cascade effect. No output schema is needed, and the description covers the relevant aspects without superfluous information.

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 input schema already provides descriptions for both parameters ('The label's unique identifier' and 'The queue's unique identifier') with 100% coverage. The description adds no further semantic information about the parameters, so it meets the baseline for high coverage.

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 clearly states the action ('Delete a label from a queue') and specifies the cascade-delete effect on assignments. It effectively distinguishes this tool from siblings like deleteQueue, deleteQueueAggregation, and updateQueueLabel.

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 implies usage (when you need to delete a label and its assignments) but does not explicitly contrast it with alternatives like updateQueueLabel or deleteQueue. It lacks direct guidance on when to prefer this tool over similar ones.

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