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

Beyond the destructiveHint/non-idempotent annotations, the description discloses that deletion may cascade to related records and — critically — that the call does not take effect until a human approves the exact request and execute_approved_action is invoked. It also notes org-configurable MCP approval rules and that business workflow approvals always apply, which materially changes how an agent should sequence the call.

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 operative instruction ("Delete vendor", cascade behavior, approval gate) is present but buried behind a generic opening sentence, and the approval requirement is restated twice — once as "configured MCP approval rules" and again as "MCP approval requirements are configurable by the organization administrator".

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, human-gated delete with an output schema, the description covers the essential mechanics: cascade risk and the approval/execute_approved_action sequencing. It stops short of saying whether the delete is permanent or reversible and what happens to the specific related records, which an agent assessing risk would want.

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%, so the single `id` parameter is documented only by its UUID format and pattern. The description never states that this is the vendor's identifier or where to obtain it, but with one obvious required UUID the gap is minor rather than blocking.

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?

"Delete vendor" names a specific verb and resource, and the opening sentence scopes it to RetailHardHat vendor records in the connected organization. It does not explicitly contrast with update_vendor or archive-style siblings, so the differentiation is inferred from the name rather than stated.

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 trigger phrase "Use this when working with RetailHardHat vendors records in the connected organization" is broad and offers no when-not conditions or named alternatives (e.g., update_vendor for modification, get_vendor to verify first). It does implicitly route the agent through the approval workflow, which is useful usage context but not selection guidance.

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