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

Annotations already declare readOnlyHint=false (indicating side effects) and idempotentHint=true (same effect on repeated calls). The description adds a reproduction instruction but does not elaborate on what happens after submission (e.g., whether a confirmation is returned, if data is persisted, or any side effects). With annotations covering the safety profile, the description adds marginal value but not rich behavioral context, so a 3 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?

The description is two sentences long and gets straight to the point. The first sentence states the purpose, the second provides a key usage hint. There is zero filler or redundancy, making it highly efficient and easy to scan.

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 three-parameter tool with no output schema, the description covers the core purpose and one parameter (conversation). However, it omits any explanation of 'message' (the required field) and 'context', and does not clarify the expected format of the conversation string (e.g., JSON array as a string). Given the tool's low complexity and existing annotations, more could be done to fully specify parameter formats, but the essential purpose is clear. A score of 3 reflects this gap.

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. It does clarify that 'conversation' is an array of recent messages for reproduction, which adds meaning beyond the raw schema (which defines it as a string defaulting to '[]'). However, it does not explain the 'message' or 'context' parameters, and the word 'array' may conflict with the schema's string type. The description provides some insight but falls short of fully compensating for the lack of 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's purpose with a specific verb ('Report') and resource ('a bug, missing feature, or send feedback'). It also adds an important detail about including the conversation array for reproduction. This unambiguously distinguishes it from sibling tools like authenticate or show_version, which serve entirely different functions.

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 explicitly states when to use this tool (to report bugs, missing features, or give feedback) and even includes a usage hint (include conversation array). While it does not mention when not to use it or name alternatives, the sibling tools are clearly unrelated, so the context is sufficient. It could benefit from a note like 'use for user-facing issues only,' but overall guidance is clear.

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