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

Annotations already indicate readOnly=false, idempotent=true, and destructive=false, which aligns with the description's write operation. The description adds minimal behavioral detail beyond stating the action and a hint about conversation inclusion, but does not mention side effects, security, or consequences of calling it repeatedly.

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, concise sentence that conveys the purpose and a key usage detail without extraneous information. It is well-structured and easily scannable.

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?

Given the complexity of three parameters and no output schema, the description omits necessary context for two parameters ('message' and 'context') and does not explain what the tool returns or how to interpret the result. It also lacks guidance on when to prefer this tool over siblings, leaving the overall context incomplete.

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. The tool description explains only the 'conversation' parameter (for reproduction) but leaves 'message' and 'context' undefined. Since 'message' is required, its purpose is unclear, and 'context' is entirely ambiguous. The description compensates for only one of three parameters.

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: reporting bugs, missing features, or sending feedback. This is specific and distinguishes it from sibling tools, none of which handle reporting.

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 provides a concrete usage instruction: 'Include the conversation array with recent messages for reproduction.' This is directly actionable. However, it does not explicitly state when to use this tool versus alternatives or when not to use it, though the purpose makes it implicit.

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