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

The description adds context about including the conversation array for reproduction, which is beyond what annotations provide. It does not mention side effects, rate limits, or idempotency, but annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false. The description doesn't contradict annotations and modestly supplements them.

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 two sentences, front-loaded with the core purpose and immediately followed by a practical usage note. There is no fluff, redundant wording, or unnecessary detail. Every sentence earns its place.

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 simplicity of the tool (3 string parameters, no nested objects, no output schema), the description covers the essential aspects: what it does and what to include. It lacks explanation of 'context' and potential return values, but for a simple tool with decent annotations, this is adequate. It could be slightly richer by clarifying all parameters.

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?

With 0% schema description coverage, the description must compensate. It explains the 'conversation' parameter by saying 'Include the conversation array with recent messages for reproduction.' However, it does not clarify the meaning of 'context' or add detail to 'message' beyond its obvious role as the report content. Partial compensation, but incomplete for all parameters.

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's purpose: 'Report a bug, missing feature, or send feedback.' This is a specific verb-action-resource combination that unambiguously indicates the tool's function. It also naturally distinguishes itself from sibling tools (auth, version, etc.) which serve different purposes.

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 a concrete usage instruction: 'Include the conversation array with recent messages for reproduction.' This guides the agent on how to invoke the tool correctly. However, it does not explicitly state when to use this tool versus alternatives, though no direct alternatives appear among siblings. The lack of explicit 'when to use / when not to use' diminishes the score.

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