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

Annotations already indicate write behavior (readOnlyHint=false) and non-destructiveness, but the description adds little context about what happens after reporting or whether authentication is needed. It also mislabels the 'conversation' parameter as an array when the schema declares it as a string, creating confusion about the expected input format.

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 with no redundant words, front-loading the core purpose. It earns its length by adding the key reproduction detail.

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 tool with no output schema and sparse parameter descriptions, the description should cover required inputs and outcomes. It omits the purpose of the required 'message' parameter, doesn't explain the 'context' parameter, and gives no indication of what response the agent should expect after reporting.

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 has 0% description coverage, so the description must explain the parameters. It only refers to the 'conversation array' for reproduction but doesn't name the parameter or clarify its format, and it ignores both 'message' (the only required parameter) and 'context', leaving their purposes ambiguous.

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 verb 'Report' and the resource ('a bug, missing feature, or send feedback'), making the tool's purpose unambiguous. It distinguishes itself from sibling tools like authenticate or show_version by specifying the reporting functionality.

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 for when to use the tool—when there is a bug, missing feature, or feedback—and instructs to include conversation data for reproduction. It does not explicitly name alternative tools or exclusions, but the purpose is clear enough that this is the obvious choice for issue reporting.

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