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

Annotations already provide readOnlyHint=false, idempotentHint=true, destructiveHint=false, which covers the safety profile. The description adds that it requires conversation data for reproduction, but doesn't disclose other behaviors like whether it blocks or how feedback is handled.

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 sentences, one for purpose and one for requirement. No fluff, every word earns its place. Front-loaded with the purpose.

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 simplicity of the tool (report bug) and the presence of annotations and required field, the description is adequate but incomplete on parameter details and return behavior. The output schema is absent but not critical for a report action. Still, more detail on 'context' and 'message' would help.

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 explains 'conversation' is an array for reproduction, but 'message' and 'context' are not explained beyond their schema names. The description adds some value but not enough for a 3-parameter tool with no schema help.

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: reporting bugs, missing features, or feedback, and specifies the action (report) and resource (bug/feature/feedback). It distinguishes from siblings like marketplace or show_version, though not explicitly from other reporting tools.

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 it (when there's a bug or feedback) but does not provide explicit exclusions or alternatives. It mentions including conversation for reproduction, which gives context on usage.

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