contacts_remove

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

With no annotations provided, the description carries the full behavioral burden and does well on the critical point: it flags the operation as destructive and explains the confirm-gate that converts a real delete into a read-only preview. It omits whether deletion is permanent/reversible and what permissions are needed, so it is strong but not complete.

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 tight sentences with the destructive nature and the gate condition front-loaded; there is no filler and every clause carries actionable information.

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 single-parameter-required mutation tool with no output schema and no annotations, the description covers the essential risk (destructive) and the safety mechanism (confirm gate / preview). It leaves minor gaps around permanence of the delete and what the preview output contains.

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% and all three parameters (contact_id, confirm, dry_run) are already documented in the schema. The description restates the confirm semantics rather than adding syntax, formats, or interactions the schema lacks, so the baseline 3 applies.

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 gives a specific verb ("Delete") plus resource ("a contact") and identifies the key ("by id"), which cleanly separates it from siblings like contacts_edit, contacts_add, or calendar_remove. An agent can select it without opening the 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?

It states the operating condition explicitly: confirm=true is required to actually delete, otherwise the call previews. That is clear when-to-use context. It does not name an alternative tool (e.g., contacts_edit when the goal is modification rather than removal), so it falls short of full routing guidance.

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