Delete Tracker entity comment

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

Annotations already declare destructiveHint=true, idempotentHint=false and readOnlyHint=false, so the safety profile is covered structurally. The description adds two useful points beyond that: it is irreversible and it returns an acknowledgement on success. It still omits permission requirements and any cascade/thread effects, so it is additive but thin.

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 short sentences, zero padding, with the destructive nature front-loaded ahead of the return-value note. Efficient, though the second sentence is minimal.

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 no output schema, the description correctly notes the return value ('an acknowledgement on success'). Params are fully covered by the schema. But for a destructive mutation it says nothing about permissions, threading behavior, or whether related replies are affected, leaving clear gaps.

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 100%, so entity_type, entity_id, comment_id, notify and notify_author are all documented in the schema itself. The description adds nothing about parameters; the baseline 3 applies when the schema does the heavy lifting.

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+resource: 'Permanently delete one comment from a Tracker entity'. An agent knows exactly what it does. However, it does not differentiate from the many sibling delete tools (notably tracker_comments_delete vs tracker_entities_comments_delete), 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?

There is no when-to-use or when-not-to-use guidance, no prerequisites, and no pointer to alternatives. The irreversibility warning is a behavioral fact, not usage routing, so the agent is left to infer context.

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