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

Annotations already declare destructiveHint=true and non-idempotence, so the description usefully adds that dependent records may be affected and that approval requirements may be configured by administrators while business workflow approvals always apply. It does not clarify whether the deletion is permanent or exactly which dependent records are impacted.

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 short and front-loads the action, with the dependent-record warning and approval note following. The approval sentence is relevant, though somewhat administrative, and nothing is bloated.

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 annotations, output schema, and single obvious id parameter, the description covers purpose, a key caution about dependent records, and approval behavior. It could be stronger by stating whether deletion is permanent or irreversible.

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 schema has only one required parameter, id, with 0% description coverage, but the description says nothing about what the id identifies or any format expectations beyond the schema's UUID pattern. It does not compensate for the lack of schema descriptions.

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 assignment_automation.' It is clear what the tool does, but it does not distinguish this tool from near siblings such as delete_team_assignment_automation or explain its scope relative to them.

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 instruction to 'Review dependent-record effects before confirming' gives implied caution for using this destructive operation, but the description never explicitly says when to choose this tool versus update, archive, or other delete variants.

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