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

Annotations already carry destructiveHint=true and idempotentHint=false, so the safety profile is known. The description adds genuinely new behavioral context that annotations cannot express: MCP approval requirements are org-admin configurable and business workflow approvals always apply, meaning the call may not take effect immediately. It stops short of saying whether deletion cascades or is reversible.

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?

Two sentences, front-loaded with the action, no filler. The approval sentence is somewhat boilerplate but is the only place that constraint appears and it is relevant to a destructive operation.

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 so return values need no explanation, and annotations cover the destructive profile. But for a two-UUID destructive tool with zero schema descriptions, the description should identify what each parameter is and whether removing an item affects templates already applied to projects — neither is covered.

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% — the schema gives only UUID formats with no semantics for 'id' or 'itemId'. The description does not clarify that 'id' is the parent task template and 'itemId' the child item, which is exactly the distinction an agent needs to avoid passing the wrong identifier.

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: 'Remove an item from a task template.' However, the sibling list contains both delete_task_template_item and delete_project_task_template_item, and the description never distinguishes a task template from a project task template, leaving real ambiguity about which resource set is being mutated.

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 vs. delete_task_template, delete_project_task_template_item, or update_task_template_item. The second sentence is about approval gating, not about tool selection, so the agent must infer usage entirely from the name.

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