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

The annotation destructiveHint=true already covers the destructive risk. The description adds 'keep first' and 'DIRECT' which provide some behavioral context beyond the annotation, but it does not disclose potential side effects (e.g., impact on references or why 'screen' is needed).

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 a single sentence with no filler. It delivers the core action, scope, and safety warning efficiently, making it easy to parse.

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 tool with 3 parameters and no output schema, the description is too sparse. It doesn't explain what 'entries' means in practice (milestones vs elements), how 'screen' filters deduplication, or what happens to duplicate children. The destructive hint and 'keep first' help, but significant context is missing.

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 coverage is 67% but the description adds no parameter detail. 'kind' and 'screen' are explained in the schema, but 'project_id' is undocumented and the description doesn't clarify its role. The relationship between parameters is implicit at best.

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 clearly states a specific action ('Remove duplicate-named entries') with a defined outcome ('keep first'), distinguishing it from deletion tools like delete_entity. The 'DIRECT, destructive' qualifier further clarifies the nature of the operation.

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 description gives no guidance on when to use this tool versus alternatives such as delete_entity or reorder. It only warns that it is destructive but does not explain scenarios (e.g., cleansing duplicate milestones before proposing new ones) or when to avoid it.

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