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

The description does not add significant behavioral details beyond the annotations. It implies sending feedback but does not disclose idempotency or side effects; annotations already cover safety (idempotent true, destructive false). The description adds no extra behavioral context.

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 concise sentences with no redundant information. It directly conveys the purpose and the key input requirement without unnecessary elaboration.

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, the description provides adequate context to use it correctly, including the explicit instruction about the conversation array. It does not require explanation of output since no output schema is present, and the purpose is clear enough.

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 description explicitly explains the 'conversation' parameter ('Include the conversation array with recent messages for reproduction') and implicitly clarifies 'message' via 'Report a bug, missing feature, or send feedback'. However, it leaves 'context' undefined, so coverage is partial.

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 function: reporting a bug, missing feature, or sending feedback. It uses a specific verb 'Report' with a clear resource, and the instruction to include conversation distinguishes it from sibling tools like authenticate or connect.

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 specific guideline to include the conversation array for reproduction, which is a direct usage instruction. However, it does not explicitly contrast with alternative tools or mention when not to use it, so it is slightly lacking in that regard.

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