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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false, covering basic safety. The description adds behavioral context by instructing to include the conversation array for reproduction, indicating the tool collects diagnostic info. It does not contradict annotations and provides additional value.

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, focused sentence that front-loads the purpose and the key instruction. It contains no fluff or redundant information, making it extremely concise and 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 3 parameters and no output schema, the description covers the essentials: purpose and the key nuance of including the conversation. The 'context' parameter remains vague, but given the tool's simplicity and the availability of annotations, the description is largely 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?

With schema description coverage at 0%, the description must compensate. It explains the 'conversation' parameter ('Include the conversation array with recent messages for reproduction') but leaves 'context' and 'message' without explicit explanation, though 'message' is self-evident as the report text. This partial compensation warrants a mid-level 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') with a specific verb and resource, and distinguishes it from sibling tools (authenticate, connect, etc.) by focusing on issue reporting. It also adds a key detail about including the conversation array for reproduction, which clarifies scope.

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 encountering a bug, missing feature, or needing to send feedback) via its clear purpose, but does not explicitly mention alternatives or exclusions. It provides clear context for usage without formal 'when-not' guidance, which aligns with a score of 4.

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