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

The description explicitly states permanence and live data modification, going beyond the destructiveHint annotation to emphasize irreversibility and the contact_id derivation. No contradiction.

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 sentences, front-loaded with critical info (permanent removal, irreversibility). No redundant words.

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 tool with 2 parameters and no output schema, the description covers the action, parameter semantics, and behavior. Lacks mention of error handling or permissions, but adequate given simplicity.

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 covers both parameters with descriptions identical to part of the tool description, so no additional meaning added beyond schema. However, the description provides context by tying contact_id to the API endpoint. Baseline 3 applies due to 100% 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 (permanently removes), resource (contact from a list), and notes the irreversible nature. It distinguishes from sibling tools like create, update, get by focusing on deletion.

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?

No explicit guidance on when to use vs alternatives. The description implies usage for permanent deletion but does not mention when not to use or alternative tools like update_contact for deactivation.

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