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

Annotations already declare destructiveHint=true and idempotentHint=true, so the destructive nature is known. The description adds context the annotations do not: the deletion is cascading, taking the config's entire check history with it, and it demands user confirmation. That is exactly the extra behavioral detail the annotations cannot express.

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?

Two short sentences, zero filler. The irreversible consequence is front-loaded and capitalized, and the confirmation requirement follows immediately after.

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 two-parameter deletion tool with no output schema and fully documented parameters, the description covers what is deleted, how far the deletion reaches, and the confirmation requirement. Only a note on how to discover existing configs (or on error behavior for a bad configId) is arguably absent.

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 100%: configId documents its provenance (from the matching get_* tool without configId) and projectId points at list_projects. The description adds no parameter-level meaning, so the baseline 3 applies.

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?

Names a specific verb (Deletes) and resource (local pack rank check config), which cleanly separates it from sibling delete_local_rank_grid_config and from create_local_pack_rank_config. No schema inspection is needed to know what it acts on.

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 one directive — 'Confirm with the user before calling' — which is a gating condition rather than a when-to-use rationale. It never states when to prefer this over alternatives such as delete_local_rank_grid_config or disabling a config instead of deleting it, so usage is only implied.

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