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

The description mentions 'report' which implies a write action, but it does not explicitly state side effects, such as creating a ticket or sending an email. With only minimal annotations (idempotentHint true, destructiveHint false), the description carries some burden but remains incomplete regarding the actual effect.

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 (two sentences), directly addresses the tool's function, and includes a specific call to action regarding the conversation parameter. No unnecessary words or redundancy.

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 description lacks details about the tool's output (e.g., a confirmation or ticket ID), whether it is asynchronous, or any required permissions. It covers the basic 'how to use' but omits post-report behavior, making it only partially complete for the user.

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 defines three parameters (context, message, conversation) with no individual descriptions. The description only explains 'conversation' as an array for reproduction, leaving 'context' and 'message' undefined. This is insufficient given the low schema coverage (0% with descriptions).

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. The verb 'report' is specific and the direct mention of these use cases makes it distinct 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 advises including the conversation array for reproduction, which is a practical usage hint. However, it does not explicitly differentiate from alternatives (though none exist for this purpose in the sibling list) or specify when to use this tool over others.

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