deleteContact

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

The description labels the tool as 'DESTRUCTIVE' and notes that the host enforces user confirmation via an approval gate. This adds behavioral context beyond the input schema, though it could mention potential side effects like cascading deletions.

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 three sentences, each with a distinct purpose: stating the action, providing usage guidelines, and noting behavioral context. It is front-loaded and contains no unnecessary 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?

The tool is simple (delete a contact). The description covers the destructive nature, usage conditions, and the host's approval mechanism. It does not specify return values, but given no output schema, this is acceptable.

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%, so the input schema already documents both parameters adequately. The description does not add additional meaning beyond the schema, earning a baseline score of 3.

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 'Permanently delete a contact by ID', specifying the verb (delete), resource (contact), and method (by ID). This distinguishes it from sibling tools like deleteCustomer or deleteContract.

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 explicitly says 'only call when the user explicitly says delete for THIS contact; never as automatic recovery from another failed operation'. It also instructs not to ask the user for re-confirmation because the host enforces it. These conditions are clear and guide correct usage.

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