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

Annotations already flag destructiveHint=true and non-idempotent, so the safety profile is covered. The description adds real value beyond that: it warns that dependent records may be affected and that organization-configurable MCP approvals plus always-on business workflow approvals can block the operation. It still does not say whether the delete is hard/irreversible or soft.

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?

Three short sentences, front-loaded with the action, then the risk warning, then the approval caveat. No filler, though the approval sentence is generic boilerplate that could be trimmed or made tab-specific.

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?

An output schema exists, so return values need no explanation, and the approval/dependency notes cover the main risk surface. What is missing is whether dependent records are cascaded or block the delete, and whether the deletion is permanent — key facts for a destructive single-parameter 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% and the single parameter (a UUID `id`) is never mentioned in the description. With coverage this low the description is expected to compensate, and it does not — the agent must infer that `id` is the diligence tab identifier. The 0-param baseline of 4 does not apply here.

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 diligence_tab" gives a clear verb and resource, but it is essentially a restatement of the tool name and title. It does not distinguish itself from near-siblings such as delete_diligence_field or list_diligence_tab, so an agent gets the basic action but no disambiguation.

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?

There is no guidance on when this should be used versus alternatives (e.g. update_diligence_tab to modify, delete_diligence_field for a single field), nor any prerequisites. "Review dependent-record effects before confirming" is a caution, not usage routing.

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