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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the safety profile is known. The description adds extra context by specifying that the conversation array should be included for reproduction, which helps the agent understand what information is expected for effective reporting.

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 immediately states the purpose and includes a key usage hint. There is no unnecessary verbiage, and the structure is ideal for quick scanning.

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, and the description covers its purpose and one parameter hint, but with no output schema and a bare input schema, it leaves gaps around the 'message' parameter, the optional 'context' field, and what happens after submission. It is adequate for basic understanding but not fully 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?

The schema has 0% description coverage, so the description must compensate. It explains the 'conversation' parameter's purpose but says nothing about 'message' or 'context'. This leaves the required 'message' parameter and optional 'context' without semantic meaning, though the overall intent is partially clear.

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 uses a specific verb 'Report' with a clear resource ('bug, missing feature, or feedback'), which makes the tool's purpose unambiguous. It stands apart from sibling tools like 'authenticate' or 'marketplace' because none of those are about reporting issues.

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 concrete guidance on what to include ('conversation array with recent messages for reproduction'), which tells the agent what context is needed. It does not explicitly name alternative tools or exclusions, but the sibling list makes the intended use clear enough.

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