delete_contact

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

With no annotations, the description carries the burden. It discloses the soft-delete behavior, which is important context beyond just 'delete'. It does not address permissions, reversibility details, or side effects on related records, but it gives a reasonable baseline for a simple delete operation.

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 two sentences, front-loaded with the action and soft-delete qualifier, followed by a concrete usage example. Every word adds value, with no redundancy or filler.

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, one parameter with full schema documentation, and no output schema, the description is nearly complete. It conveys the action, the soft-delete nuance, and usage format. It could mention return values or undo options, but these are not essential for such a straightforward operation.

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 coverage is 100%, and the parameter is already described as 'The contact ID (UUID)'. The description's example reinforces this but adds no new semantic information beyond what the schema provides, so the baseline score of 3 is appropriate.

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 tool deletes a contact from the CRM and explicitly notes it's a soft delete. This distinguishes it from sibling tools like delete_website or create_contact/update_contact, making the purpose unambiguous.

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 example 'Delete contact <id>' provides direct usage guidance, and the mention of 'soft delete' sets expectations about what the operation does. However, it does not explicitly contrast with alternatives or state when not to use it, but the simplicity of the tool makes this less critical.

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