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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so the safety profile is partly covered. The description adds meaningful context beyond annotations by explicitly calling it a 'soft delete' and noting progress counters are recomputed automatically—behavior a caller would not infer from annotations alone. It could go further on reversibility or authorization, but this is a solid contribution.

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?

A single efficient sentence that front-loads the action and resource, then adds two key behavioral notes in a tight parenthetical and trailing clause. Zero waste.

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 an output schema present, the description needn't explain return values, and annotations cover the safety hints. What remains important—soft-delete semantics and counter recomputation—is provided. Given a 2-parameter mutation tool with low schema coverage, a bit more on ID semantics or error cases would fully complete it.

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% for the 2 parameters (report_id, item_id), so the description must compensate. It names both concepts implicitly—'one item' (item_id) and 'a report's diligence checklist' (report_id)—providing meaning beyond the bare type declarations. However, it doesn't specify ID formats or whether item_id is scoped globally or per report, leaving a 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?

States a specific verb (remove) and resource (a report's diligence checklist item), clearly distinguishing from siblings like add_diligence_item and update_diligence_item. The parenthetical '(soft delete)' further clarifies the operation type. It lacks explicit references to those siblings by name, so it falls short of a 5.

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?

No guidance on when to use this tool versus alternatives like update_diligence_item or the checklist-generation tools. There are no stated prerequisites or contexts. The description only describes what it does, not when to invoke it.

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