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

Annotations already flag destructiveHint=true; the description adds genuinely new context: cascading dependent-record effects and the governance fact that organization-configurable MCP approvals apply while business workflow approvals always apply. It does not state whether deletion is recoverable or what happens to in-flight approvals, keeping it short of a 5.

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 and immediately followed by the caution. The final sentence on organization-configurable MCP approvals is slightly tangential but still earns its place as governance context.

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?

With annotations covering the safety profile and an output schema present, the description supplies the remaining operational context an agent needs to call this destructive tool responsibly. Only the parameter's identity and recoverability are left unaddressed.

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 only parameter is 'id' with 0% schema description coverage, and the description says nothing about what the id refers to, its format, or where to obtain it. The description adds no parameter meaning beyond the raw JSON schema type/pattern.

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?

States a specific verb and resource ('Delete approval_flow'), which is unambiguous against the many other delete_* siblings since the noun is named explicitly. It does not explicitly contrast with update_approval_flow or get_approval_flow, but the verb itself does that work.

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?

'Review dependent-record effects before confirming' implies a pre-deletion check but never says when deletion is appropriate versus alternatives (e.g., deactivating/updating the flow), nor does it state prerequisites. Usage is inferable but not explicitly guided.

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