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

Annotations already declare destructiveHint=true, so the agent knows this is destructive. The description adds useful context beyond annotations by warning about dependent-record effects and noting that approval requirements are organization-configurable while business workflow approvals always apply.

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 front-loaded with the action and is appropriately short. The first sentence largely restates the name, and the approval sentence is somewhat generic, but overall it is efficient and easy to scan.

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, and annotations cover the destructive profile, so the description does not need to explain return values or basic safety. It adds relevant deletion cautions and approval context, though it could be more explicit about what dependent records may be affected.

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?

There is one required parameter, 'id,' and the schema defines its UUID format and pattern but provides no textual description. The description does not add meaning about what the id identifies, so with 0% schema description coverage it only minimally compensates for this gap.

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 team_assignment_automation.' This is clear enough to identify the operation, but it does not distinguish this tool from the closely related sibling 'delete_assignment_automation' or explain how team assignment automation differs from assignment automation.

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 only guidance is 'Review dependent-record effects before confirming,' which is a caution rather than a when-to-use instruction. The description does not say when this deletion tool should be chosen over alternatives such as updating or deactivating the automation.

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