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

Annotations indicate readOnlyHint=false and destructiveHint=false, consistent with a non-destructive write operation. The description adds context about the tool's purpose (reporting to a team) and constraints (one issue per call, no duplicates), which goes beyond annotations. However, it does not detail the internal behavior (e.g., how feedback is stored or who receives it), but that is acceptable for a simple feedback tool.

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?

The description is moderately concise (four sentences) and well-structured: first sentence states purpose, second lists usage conditions, third gives a sanity check rule, and fourth provides usage constraints. Every sentence adds value without redundancy. Slightly longer than necessary but still effective.

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?

Given the tool's simplicity (3 parameters, no output schema, no nested objects), the description covers all necessary aspects: when to use, what to include in content, how to handle observations vs. user reports, and constraints. An agent can reliably decide to invoke this tool and format the call correctly based on the description alone.

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%: all three parameters have descriptions. The tool description reinforces the 'content' parameter with additional guidance (quote exact sentence, no personal info), but adds minimal new meaning beyond the schema. Baseline is 3, and the description does not significantly elaborate on parameters beyond what is already in the input schema.

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 states the tool is for reporting documentation issues in BlockRazor. It uses a specific verb ('Report an issue') and resource ('documentation of BlockRazor'), and distinguishes from sibling tools (askQuestion, getPage, searchDocumentation) by specifying it is only for reporting problems, not for asking questions or searching.

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 provides explicit when-to-use conditions: when encountering outdated, contradictory, or missing info, or when the user reports a problem. It also gives when-not-to-use (do not use to confirm accuracy), and includes guidelines like one call per issue, not reporting same issue twice, and a sanity check before reporting.

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