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

Annotations already inform the agent that the tool is idempotent and non-destructive (idempotentHint=true, destructiveHint=false). The description adds useful reproduction guidance ('Include the conversation array with recent messages for reproduction') but does not disclose any extra behavioral side effects or limitations beyond that.

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, front-loaded sentence that immediately states the purpose and then gives the one key operational instruction. No filler or unnecessary repetition.

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 a single required string parameter and low expected complexity, the description covers the core use case and the important reproduction hint. It is slightly incomplete around the exact meaning of the remaining optional parameters and the mismatch between description and schema for 'conversation', but overall the tool is sufficiently describable in one sentence.

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 provides zero description coverage, so the description must carry the parameter interpretation. It explains that 'conversation' should include recent messages for reproduction, but incorrectly calls it an 'array' while the schema defines it as a string (likely a serialized JSON array). The 'message' and 'context' parameters receive no explanation beyond their names and defaults.

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 verb ('Report') and the possible resources ('a bug, missing feature, or feedback'). It is specific and distinct from sibling tools like authenticate, show_version, and marketplace, 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?

It clearly indicates when to use the tool: whenever a bug, missing feature, or general feedback is intended. It does not explicitly name exclusions or alternative tools, but the context is unambiguous and no competing sibling exists for this purpose.

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