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

The annotations already declare destructiveHint=true and idempotentHint=true, but the description adds important context: the record removal cannot be undone by another tool. It also discloses authentication and workspace-claim preconditions, including a specific 403 refusal mode for unclaimed sandbox workspaces.

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 short, front-loaded with the action and required parameter, and then adds irreversible-deletion and authentication context. Every sentence contributes useful information without unnecessary preamble.

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 destructive mutation with no output schema, the description covers the key safety and access constraints: record removal is irreversible and requires a claimed credential and workspace. It does not describe behavior for missing contacts or related-record effects, but the core context needed to call it correctly is present.

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 the single contact_id parameter is already documented as a UUID shown by list_contacts. The description repeats 'pass contact_id' but adds no format, validation, or lookup guidance beyond what the schema provides.

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 states a specific verb and resource: 'Delete a contact.' It also names the required identifier, making the operation immediately distinguishable from sibling contact tools such as get_contact, update_contact, and list_contacts.

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 gives prerequisites for use, notably the claimed credential and claimed workspace requirements, including the sandbox 403 behavior. However, it does not explicitly say when to use this tool versus alternatives like update_contact, or whether deletion is appropriate only in specific lifecycle situations.

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