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

Annotations already declare destructive=true, readOnly=false, and idempotent=false, so the safety profile is known. The description adds meaningful behavior beyond the annotations: it requires organization administrator permissions, no change occurs until human approval in Settings > MCP followed by execute_approved_action, and business workflow approvals always apply. It does not detail what related records are affected or whether the deletion is reversible, but the approval gating is a strong disclosure.

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 not bloated, but it is not front-loaded: the first sentence is generic boilerplate before the actual 'Delete a contact' purpose. The approval and permission sentences earn their place, but the opening could be removed or merged without losing meaning.

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 one-parameter delete, the description covers the key operational context: admin permissions, the human approval gate, execute_approved_action, and configurable vs business workflow approvals. An output schema exists, so return values need not be explained. It could still be stronger by noting deletion scope or irreversibility, but it is largely complete for this tool.

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 0% for the single contactId parameter, so the description must compensate, and it does not. It never explains what contactId represents, how to obtain it, or what format is expected beyond the schema's UUID pattern. The agent can infer it is an ID from the schema, but the description adds no semantic guidance.

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 scopes the tool to RetailHardHat contacts in the connected organization, which distinguishes it from the many other delete_* siblings. It does not explicitly contrast with update_contact or list_contacts, but the core operation is 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 opening sentence ('Use this when working with RetailHardHat contacts records') is generic contextual framing rather than a real when-to-use rule. The description gives important prerequisites around administrator permissions and approval, but it never names alternatives such as update_contact or explains when deletion is preferable to another operation.

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