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

The description adds significant behavioral detail beyond the annotations: it discloses that the operation is subject to MCP approval rules, may cascade to related records, requires human approval in Settings > MCP, and that execute_approved_action must be called. These are critical traits for a destructive operation and are not captured by the destructiveHint annotation alone.

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 four sentences and front-loads a vague context phrase before the core action. It contains some redundancy (e.g., repeating that approval requirements are configurable) and could be tightened, but the key behavioral information is present.

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 destructive nature and approval workflow complexity, the description does well to cover cascade and human-approval requirements. An output schema exists so return values need not be explained. However, the complete omission of parameter semantics for the single required ID leaves a critical gap for correct invocation.

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?

The input schema has one required parameter (id) with 0% description coverage, and the tool description does not mention the parameter at all. It fails to explain what the id represents or how to obtain it, leaving the agent without guidance beyond the raw schema.

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 explicitly states 'Delete permit' and ties it to RetailHardHat permits records, which clearly distinguishes it from update_permit or get_permit. The opening sentence 'Use this when working with RetailHardHat permits records' is somewhat vague but the core verb+resource 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 description gives context about approval requirements and cascading effects, which implies when this tool is appropriate (i.e., under human-approved deletion workflows). However, it does not explicitly compare to alternatives like update_permit or delete_permit_document, nor does it state when NOT to use it. Usage is implied rather than clearly guided.

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