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

Annotations already indicate the operation is idempotent, non-destructive, and not read-only. The description adds behavioral context by specifying the need to include recent messages as a conversation array for reproduction, which is a key requirement not visible in the annotations. No contradiction exists with the annotations.

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 concise sentences with no filler. It front-loads the core purpose (report bug/feature/feedback) and then supplies the most critical usage detail (include conversation array). 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 tool's simple interface (3 flat parameters, no output schema) and supporting annotations, the description covers the essential purpose and one key input requirement. It lacks details about the return value or post-submission behavior, but for a feedback-reporting tool this is sufficient.

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 0%, so the description must compensate. It explicitly explains the 'conversation' parameter as an array of recent messages for reproduction. The required 'message' parameter is implicitly clear from the tool's purpose, but 'context' receives no explanation, leaving a gap. This is marginally acceptable but not fully compensating.

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 a clear verb and resource: 'Report a bug, missing feature, or send feedback.' This precisely defines the tool's action and distinguishes it from sibling tools like authenticate, show_version, and marketplace, which serve entirely 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 implies when to use the tool (when a bug, missing feature, or feedback needs to be submitted) and gives a specific instruction to include the conversation array for reproduction. It does not explicitly state when not to use it or mention alternatives, but no sibling tool overlaps, so the usage context is clear.

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