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

Annotations cover the safety profile (readOnly=false, destructive=false), so the bar is lower, and the description adds real behavioral content: write in the user's own words and never include file contents, credentials, or personal data they did not ask to share. It does not describe confirmation, delivery, or rate-limit behavior, so it stops short of a 5.

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 tight sentences with the purpose front-loaded, then trigger conditions, then content constraints. Each sentence carries weight; the only minor cost is that the privacy constraint sentence is somewhat long.

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 fire-and-forget send with no output schema, the description covers purpose, triggers, and content constraints adequately. It does not indicate whether the user should be given confirmation or how the send is delivered, a small gap for a 3-parameter mutation.

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 schema already documents kind, rating, and message semantics. The description restates the enum meanings and the 'in the user's words' constraint but adds no syntax or format detail beyond the schema, making the baseline 3 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?

States a specific verb (send) plus the resource (the user's feedback about BCD to the BCD team) and enumerates the kinds handled (bug, feature request, praise). No sibling tool does anything comparable, so an agent can distinguish it immediately.

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?

Explicitly states the two triggering conditions: 'when the user asks to report something to BCD, or accepts your offer to.' It also constrains the message content, which is the relevant 'how' guidance here since no alternative tool competes for this task.

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