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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false. The description goes beyond that by disclosing reversibility via helpwise_reopen_conversations and confirming no customer-facing notification — exactly the context an agent needs before invoking a destructive op.

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?

Four short clauses, front-loaded with the 'WRITE:' marker so the mutation nature is visible immediately. Every clause carries distinct information (scope, reversibility, side effects, endpoint) with no filler.

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 mutation with full annotation coverage and no output schema, this covers scope, reversibility, and side effects adequately. Minor omission: it doesn't state the effect of closing an already-closed conversation, though idempotentHint partly covers that.

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% and there is a single parameter, so the schema already documents the array, its item type, and the 1-25 bounds. The description's 'up to 25' reinforces maxItems but adds nothing beyond the schema; baseline 3 applies.

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 ('close up to 25 conversations'), gives the scope limit, and clarifies intent with '(mark them done)'. It also names the sibling helpwise_reopen_conversations, so an agent can place it precisely among the 21 tools.

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?

Provides clear context for selecting this tool over siblings: it names the undo path (reopen) and asserts 'Nothing is sent to customers', which distinguishes it from helpwise_send_email or helpwise_add_note for a superficially similar end state. No explicit 'when not to use' statement, but the routing signal is strong.

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