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

Annotations already declare idempotentHint=true and destructiveHint=false, so the description adds minimal extra behavioral info. It adds the context of requiring the conversation array, but does not explain what happens after submission (e.g., ticket creation). With annotations covering safety, this score is appropriate.

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 the first stating the primary purpose and the second providing actionable guidance on required inputs. No fluff, well-structured.

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 simple reporting tool with no output schema, the description sufficiently covers purpose and key input guidance. It lacks detail on optional parameters and post-submission behavior, but given the tool's simplicity and the annotations, it is reasonably complete.

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 no descriptions for parameters, so the description must compensate. It explains the 'conversation' parameter explicitly, and implies 'message' is the report contentaa, but 'context' is not addressed at all. Partial compensation leads to a marginal score.

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: 'Report a bug, missing feature, or send feedback.' It specifies the resource (bug/feedback) and the action, distinguishing it from siblings like authenticate or show_version which serve unrelated 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 gives clear guidance on what to include ('Include the conversation array with recent messages for reproduction'), which tells the agent how to properly use the tool. It does not explicitly mention when not to use it, but given the unrelated sibling tools, this is adequate.

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