delete_contact

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

The description simply restates the action 'delete' without adding behavioral context beyond what annotations already declare. Annotations provide destructiveHint=true, readOnlyHint=false, idempotentHint=true, but the description does not add information about permanence, side effects, or related data. It adds no value over the structured annotations.

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, front-loaded sentence with no filler. It is as concise as possible while still being clear, earning full marks for conciseness.

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 simple delete operation with one parameter and annotations covering destructive behavior, the description is minimally complete. However, it lacks usage context and does not mention what happens after deletion or any side effects (beyond destructiveHint). The absence of an output schema and lack of guidance make it adequate but not rich, so a score of 3 is appropriate.

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%: the only parameter contact_id has a description 'the id of the contact'. The tool description itself does not elaborate on the parameter, but the schema already fully covers its semantics, satisfying the baseline for a fully-documented schema.

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 'Delete a contact' uses an explicit verb and resource, making it immediately clear what the tool does. It distinguishes from sibling tools like delete_contact_group and delete_contact_relation by specifically targeting a contact, so there is no ambiguity.

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 usage guidance is provided. The description does not indicate when to use this tool versus alternatives like update_contact or restore_contact, nor does it mention any prerequisites or contexts where deletion is appropriate. The annotations include destructiveHint but no practical guidance is offered.

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