Delete a contact

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

With no annotations, the description carries the full burden. It only states 'Delete a contact,' implying a destructive operation, but does not disclose whether deletion is reversible, cascading effects, or required permissions. This is insufficient for an AI agent to understand behavior.

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 very short but includes unnecessary 'Tags: Contacts.' It front-loads the HTTP method and action, which is acceptable, but the tag line is extraneous and could be omitted without loss.

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 simple tool (1 param, no output schema), the description should still explain the required parameter and expected result. It does neither. The agent is left guessing about what happens after deletion.

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%. The input schema shows a required nested 'id' parameter, but the description provides no explanation of the parameter or its format. The agent must rely solely on the schema, which lacks descriptions. The description adds zero value here.

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 verb and resource: 'Delete a contact.' It distinguishes from other delete tools by specifying 'contact', though it doesn't elaborate further. The addition of the HTTP method is redundant but not harmful.

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 is provided on when to use this tool versus alternatives like delete_task or delete_project. The description mentions the HTTP method but gives no context for selection.

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