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

Annotations indicate the tool is idempotent and non-destructive, but the description doesn't elaborate on side effects like sending a report or creating a ticket. It adds minimal behavioral context beyond what annotations already imply.

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 concise, consisting of two clear sentences with no redundant information. It directly conveys the tool's purpose and a key requirement for the conversation parameter.

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 covers the essential action and the need for conversation data. It does not specify the outcome or confirmation after reporting, but this is somewhat mitigated by the idempotent annotation and the simple nature of the task.

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% for parameters. The description only clarifies the 'conversation' parameter by mentioning it should contain recent messages for reproduction, leaving 'context' and 'message' unexplained. This is insufficient compensation for the lack of parameter details.

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 bugs, missing features, or sending feedback. It is specific and distinguishes itself from sibling tools that likely serve different purposes like authentication or marketplace.

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 implies usage when a bug or feedback needs to be reported, but does not explicitly state when to use this tool over alternatives. It lacks guidance on conditions or exclusions, though it does mention including the conversation array for reproduction.

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