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

Annotations already indicate readOnly=false, idempotent=true, and destructive=false, so the description does not need to repeat these. However, it adds no extra behavioral context—such as what happens after reporting (e.g., sent to developers, stored in a system) or whether any side effects occur beyond the action. With annotations present, the bar is lower, but the description still lacks useful behavioral details.

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 a single, concise sentence that front-loads the purpose and adds the key usage tip about including conversation data. There is no redundant information, and it is appropriately brief for a simple reporting tool.

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 low complexity (3 parameters, no output schema), the description covers the core purpose and one essential usage hint. However, it omits the meaning of the 'context' parameter and does not clarify the format of the 'conversation' string, leaving some gaps. It is minimally adequate but not fully complete.

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?

The schema has 0% description coverage, so the tool description must compensate for parameter meanings. It only mentions the 'conversation' parameter ('Include the conversation array...') and implicitly the 'message' as the content of the report, but the 'context' parameter is entirely unaddressed. This is insufficient for a tool with three parameters and no schema descriptions.

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 clearly states the tool reports bugs, missing features, or feedback, and it is distinct from sibling tools like authenticate or show_version. The verb 'report' combined with the resource 'bug/feature/feedback' is specific enough, though it could be more precise about the exact channel or scope.

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 implies when to use this tool (for reporting issues) but does not explicitly contrast with alternatives or provide exclusion criteria. The instruction to 'Include the conversation array with recent messages for reproduction' is a usage hint but not a full guideline on when to choose this over other tools.

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