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

Annotations already carry destructiveHint=true and readOnlyHint=false, and the description adds materially richer safety context: unconfirmed calls return confirmation_required with a payload preview, confirmWrite: true only applies after explicit user confirmation, and preflight is not confirmation. It also narrows the blast radius by scoping the action to the MCP server session.

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 sentences, no wasted words: the core action and scope are front-loaded, then the unconfirmed path, the confirmed path, and the preflight caveat each get one earned sentence. Nothing duplicates the schema or annotations.

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 gated tool with no output schema, it discloses the unconfirmed response (confirmation_required plus payload preview) but not the confirmed/success response. More importantly, it never mentions confirmClear — the parameter literally named for this action — so an agent cannot be certain of the full confirmation protocol.

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 the baseline is 3 and the description need not restate parameter docs. It adds flow-level meaning around confirmWrite, but it never clarifies the relationship between confirmClear and confirmWrite, leaving an agent unsure whether one or both booleans must be true.

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?

The description names a specific verb, resource, and scope: 'Clear the Red audit log for this MCP server session.' It distinguishes cleanly from the viewing sibling brc_list_audit_log and from the brc_clear_company_api_key / brc_clear_all_company_api_keys tools, which target a different resource.

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 explains how the confirmation flow works but never states when to choose this tool versus alternatives; brc_list_audit_log is not named as the viewing counterpart, nor are the other clear-* siblings excluded. Usage is implied by the name and scope rather than explicitly routed.

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