delete_contact

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

The description implies a destructive action but does not disclose behavioral traits like irrevocability, required permissions, or side effects (e.g., cascading deletions). With no annotations, the description carries the full burden but fails to provide necessary 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?

The description is very short and front-loaded, which is efficient, but it lacks sufficient detail to be fully helpful. Every word earns its place, but more content is needed.

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 one-parameter tool, the description is minimally complete but fails to cover behavioral context (e.g., permanence of deletion, required permissions). The lack of output schema and annotations increases the burden on the description.

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?

The description adds no meaning beyond the input schema for the single parameter 'contact_id'. Despite 0% schema description coverage, the parameter name is self-explanatory, but the description could clarify expected format or source.

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 ('CRM contact'), making the purpose immediately understandable. However, it does not differentiate from sibling tools like delete_routing_form or delete_webhook, though the resource type is distinct.

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 (e.g., bulk_create_contacts or update_contact). Prerequisites, such as whether the contact must exist or have no dependencies, are absent.

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