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

Annotations already indicate readOnlyHint=false, destructiveHint=false, and idempotentHint=true, covering safety and idempotency. The description adds minimal behavioral context beyond stating the action (reporting) and the instruction to include conversation for reproduction. It does not describe side effects (e.g., ticket creation) or any rate limits, but given the annotations cover the basics, a score of 3 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, front-loaded with the core purpose, and contains zero filler. Every sentence earns its place—the first states the action, the second provides the key invocation detail. This is exemplary conciseness.

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 tool with no output schema and basic annotations, the description covers the essential usage (reporting and including conversation) but omits explanation of the 'context' parameter and does not describe the expected response or outcome. It is sufficient for basic invocation but lacks completeness for fully informed use, especially given the absence of parameter descriptions in the schema.

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%, so the description must compensate. It clarifies the 'conversation' parameter explicitly ('Include the conversation array...'), which is helpful. However, it does not mention the 'context' parameter at all, and 'message' is self-evident from the name. The description adds some meaning but does not fully cover all three parameters, so it partially compensates for the lack of schema descriptions.

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 with a specific verb ('Report') and enumerates three distinct use cases (bug, missing feature, feedback). This is concise and unambiguous, and it clearly differentiates from sibling tools like 'authenticate' or 'marketplace' which serve entirely different 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 explicit guidance to include the conversation array for reproduction, which helps the agent know how to invoke the tool. However, it does not explicitly state when NOT to use this tool or mention any alternative tool for similar purposes. Given the sibling tools are unrelated, the lack of exclusions is acceptable, but explicit caveats would be stronger.

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