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

Annotations already indicate readOnlyHint=false, idempotentHint=true, and destructiveHint=false. The description adds the instruction to include the conversation array for reproduction, but does not disclose deeper behavioral aspects such as whether a report is sent immediately, any rate limits, or what happens on repeated submissions. It does not contradict 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, front-loaded with the tool's purpose and followed by a direct usage instruction. No wasted words; every sentence adds value.

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?

The tool has 3 parameters and no output schema, so the description should explain what happens after reporting and cover all parameters. It does not describe the 'context' parameter, nor does it mention any return value or post-submission behavior. This leaves significant gaps for an agent trying to use the tool correctly.

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 only clarifies the 'conversation' parameter ('Include the conversation array with recent messages for reproduction'), but leaves 'message' and 'context' unexplained. 'message' is required and its content is only implied by the tool's purpose. The description adds partial meaning but is insufficient for all three 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 with a specific verb: 'Report a bug, missing feature, or send feedback.' It identifies the resource (bug/feedback) and distinguishes itself from sibling tools like authenticate and connect, 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 provides clear context on when to use the tool: to report bugs, missing features, or send feedback. It also gives a specific usage instruction to include the conversation array for reproduction. However, it does not explicitly mention exclusions or alternatives, though no sibling tool serves the same purpose.

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