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

Annotations already provide safety traits (readOnlyHint=false, idempotentHint=true, destructiveHint=false). The description adds the requirement to include the conversation array but doesn't disclose additional behavioral traits such as side effects or response behavior. No contradiction with 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 a single sentence that front-loads purpose and follows with usage guidance. No unnecessary words.

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 is simple, but the description omits any mention of what happens after a report is submitted or how the response is handled. Given the lack of an output schema, this is a gap, though the annotations cover safety. It's adequate for a straightforward reporting tool.

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%. The description highlights the conversation parameter for reproduction, but doesn't clarify the required 'message' parameter or the optional 'context' parameter, leaving the agent to infer their meaning. This is insufficient for a tool with one required parameter.

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 resources: bug, missing feature, and feedback. It effectively distinguishes from siblings like show_version and toolkit_info, which are informational 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?

It provides clear context for when to use (reporting issues or sending feedback) and includes an explicit instruction to include the conversation array for reproduction. However, it doesn't explicitly state exclusions or alternative tools.

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