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

Annotations already declare destructiveHint=true, so the bar is lower. The description reinforces this with 'WRITE, DELETES DATA' and adds the concrete DELETE endpoint, which confirms a hard delete rather than an archive. However, it says nothing about irreversibility, required permissions, or side effects on related records.

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?

Two short sentences, front-loaded with the destructive-write warning followed by the endpoint. Every clause earns its place; the all-caps prefix is slightly loud but serves as an effective safety flag.

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 two-parameter delete with full schema coverage and a destructiveHint annotation, the description covers purpose, target, and API mapping adequately. Only irreversibility/error behavior is left unstated, which is a minor gap given no output schema exists.

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 100% for both parameters (customer id and contact id), so the schema already carries parameter meaning. The REST path echoes the {id}/{contact_id} mapping but adds no new semantics beyond what is documented.

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 (remove/delete) and resource (one contact from a customer), and the REST mapping (DELETE /customers/{id}/contacts/{contact_id}) removes any ambiguity about the target entity. An agent can distinguish this from enchant_add_customer_contact and enchant_update_customer without opening a schema.

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 phrase 'remove one contact' implies per-contact granularity rather than bulk deletion, but there is no explicit when-to-use, when-not-to-use, or mention of alternatives. No prerequisites or confirmation requirements are stated.

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