Delete Contact

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

The annotation destructiveHint already indicates the tool is destructive. The description adds that confirm must be true, which is a behavioral guard. However, it does not disclose side effects (e.g., permanent deletion, cascading effects) or behavior when confirm is false.

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 extremely concise: two short sentences that front-load the action and the key requirement. No extraneous words, every sentence adds value.

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?

Given the tool's simplicity and the presence of an output schema, the description covers the essential purpose and the confirm requirement. However, it lacks details on what happens if confirm is not true, how to obtain a contact_id, or when to use it vs. other contacts tools, leaving some gaps for an agent.

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 0%, so the description must explain parameters. It implicitly mentions contact_id ('by id') and states confirm=True is required, but does not define the format of contact_id or the behavior of confirm (default false, must be true to delete). This leaves ambiguity.

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) and the resource (a contact by id), making the purpose immediately understandable. It does not explicitly differentiate from sibling tools like contacts_update, but the verb 'delete' is distinct enough for most agents.

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 mentions the required confirm=True, which is a precondition for usage, but provides no guidance on when to choose this tool over alternatives (e.g., contacts_update, contacts_search). No context about prerequisites (e.g., contact must exist) or when not to use it.

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