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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is carried by structured data. The description adds one genuinely useful behavioral fact — the write-scope requirement — but says nothing about irreversibility, cascading effects on associated data, or error behavior for a missing ID.

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, action first then the permission requirement, with zero filler. Nothing is wasted or buried.

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 single-parameter destructive delete, annotations supply the destructiveness signal and the description supplies the auth requirement, leaving little an agent needs to guess. A note on what happens if the trigger does not exist would close the only real gap.

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%; the single `id` parameter is documented as "comment trigger ID" with a uuid format. The description adds no meaning beyond that, so the baseline 3 is appropriate.

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?

"delete a comment trigger" states a specific verb and resource, so the agent knows exactly what entity is removed. It does not explicitly distinguish itself from siblings like update_responder_comment_trigger or list_responder_comment_triggers, but the name/description pairing is unambiguous.

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 adds a prerequisite ("requires write scope") but gives no explicit when-to-use or when-not-to-use guidance, and never mentions the update/disable alternative that a sibling tool might offer. Usage is only implied by the verb.

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