delete_contact

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

With no annotations and no output schema, the description carries the full burden of behavioral disclosure. It says nothing about whether deletion is permanent, what permissions are required, or what happens on success/failure. 'Delete' implies destruction but offers no safety or reversibility context.

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?

Extremely concise at three words, front-loaded with the action. It is appropriately sized for a no-param tool, though it borders on being too terse to be useful.

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 operation with no annotations, no output schema, and no parameter guidance, the description is inadequate. An agent needs to know if deletion is irreversible, if authentication is required, and what the effect is on related data. None of this is provided.

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?

Zero parameters, so the schema coverage is 100% and there are no parameters to document. Per the rules, 0 params yields a baseline of 4. The description adds nothing but also needs to add nothing.

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?

States a specific verb (Delete) and resource (contact), clearly distinguishing it from sibling add_contact and import_contacts. However, the description is minimal and provides no additional scope or detail beyond the core action.

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 guidance on when to use this tool versus alternatives like block or unblock, nor any prerequisites or warnings. The description is a bare statement with no contextual help for an AI agent.

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