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

Annotations already indicate idempotentHint=true and readOnlyHint=false, so the description does not contradict them. The description adds limited behavioral context, primarily the reproduction instruction. It doesn't explain what happens after submission (e.g., confirmation, response format), but with annotations covering safety aspects, a mid-range score is appropriate.

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?

Two concise sentences with no filler. The first sentence states the purpose, the second provides critical usage guidance. The description is front-loaded and every word 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?

For a simple tool with three parameters and no output schema, the description adequately covers the primary purpose and one key parameter. However, it omits details about the remaining parameters and the expected response/return behavior. Given the tool's simplicity and annotations, this is a minimum viable description with clear gaps.

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 0%, so the description must compensate for parameter meanings. It explicitly explains the 'conversation' parameter ('Include the conversation array with recent messages for reproduction'), but leaves 'message' and 'context' under-explained. The required 'message' is the core input and is not described, which is a significant gap.

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?

Description clearly states the tool's purpose with a specific verb+resource: 'Report a bug, missing feature, or send feedback.' It is distinct from sibling tools like authenticate, connect, and show_version, making it easily distinguishable.

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 clear context on when to use the tool (bug, missing feature, feedback) and gives a specific usage directive: 'Include the conversation array with recent messages for reproduction.' No explicit exclusions or alternatives are mentioned, but siblings are clearly different in scope.

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