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

Annotations include idempotentHint=true, indicating the operation can be repeated without different effects, and destructiveHint=false. The description adds that it's for reporting issues and suggests including conversation context, but doesn't detail side effects like whether data is sent externally, rate limits, or authentication needs. Since idempotent and non-destructive are already declared, the description adds modest context but not deep transparency.

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, concise and front-loaded. The first sentence states the purpose, and the second provides a key usage hint. No waste, but it could be slightly more structured by explicitly naming parameters.

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?

Without an output schema, the description doesn't need to explain return values. It covers the main purpose and hints at reproduction steps. However, for a tool with three parameters and no param descriptions, it could explain the 'context' parameter and clarify how the conversation array should be formatted. It's adequate but not comprehensive.

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%, and the description mentions 'Include the conversation array' which gives context for the 'conversation' parameter. However, it doesn't explain 'context' or 'message' beyond what the schema provides. With no param info in schema, the description partially compensates but not fully; 'message' is obvious as required, but 'context' is unexplained.

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?

Description clearly states the tool's purpose: 'Report a bug, missing feature, or send feedback.' It specifies the verb 'report' and the resource (bug/feature/feedback), and it distinguishes itself from siblings like show_version and toolkit_info by focusing on reporting issues rather than querying information.

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 this tool (when you need to report a bug or feedback), but it doesn't explicitly state when not to use it or provide alternatives. It mentions including the conversation array for reproduction, which gives some context, but lacks exclusions or comparison to other tools.

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