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

Annotations already declare readOnlyHint=false, destructiveHint=true, idempotentHint=false, openWorldHint=true. The description reinforces the write gate ('confirm:true required') and narrows the effect to an internal note, which is useful context. It does not explain why the operation is flagged destructive, nor what the confirm gate is protecting against, so the addition is modest.

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?

Front-loaded with 'WRITE:' and the confirm requirement, which is correct. The third sentence is a compressed, ambiguous fragment ('ticket / add_note with notetype 1') that costs clarity without earning its place.

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 3-parameter mutation with full schema coverage and complete annotations, the description covers the write/confirm gate and the internal (non-client-visible) scope. It omits what the tool returns, whether the note is immediately visible to staff, and any error conditions — acceptable but not complete for a destructive-flagged write.

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 coverage is 100%, so the schema already documents note, confirm, and client_id — baseline 3. The phrase 'notetype 1' does add a semantic mapping not present in the schema (internal note = note type 1), but it is unexplained shorthand rather than actionable guidance.

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 ('add an internal note to a client record'), which distinguishes it from the sibling vision_add_ticket_note by scope (client vs ticket). The trailing fragment 'ticket / add_note with notetype 1' is cryptic and muddies an otherwise clear statement, keeping it from 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?

'WRITE: confirm:true required' gives a precondition, and 'internal note' implies the when-not case (nothing client-visible or emailed). However, it never explicitly names vision_add_ticket_note as the alternative for ticket-scoped notes, leaving the routing to inference.

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