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

Annotations already flag destructiveHint=true and idempotentHint=true, yet the description still adds substantial value: the deletion is soft in effect (a full copy is retained in workspace Logs) and the audit record captures who, from which IP, and when. That recoverability and audit-trail information is exactly the kind of consequence an agent cannot get from the annotations.

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?

Three short sentences, each carrying distinct information: scope, consequence/audit behavior, and the invocation gate. The action is front-loaded and nothing is redundant with the title.

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 destructive, no-output-schema tool, the description covers scope, permission model, audit/recoverability, and the call gate — enough to invoke it safely. The only gap is that it does not say what a successful response looks like or how to confirm the note is gone.

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 all four parameters are already documented, including noteId's pointer to list_conversation_notes and authorName's audit-log purpose. The description adds no parameter-level detail beyond the phrase "that note," so the baseline of 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 ("Delete one note") and the singular "one" distinguishes it from bulk operations like bulk_delete_kb_docs. It never names the adjacent siblings (update_conversation_note, list_conversation_notes, delete_conversation), so the agent must infer scope from the tool name, but the intent 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?

"Only call when the user asked to delete that note" gives a clear gating condition and implicitly excludes proactive/agent-initiated deletion. It also states the permission model (any user with access may delete any note), which tells the caller no ownership check is needed. No explicit alternative-tool routing (e.g. update to blank vs delete) is offered.

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