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

Annotations already declare the tool as idempotent (idempotentHint: true) and non-destructive (destructiveHint: false). The description adds the reproduction context via the conversation array but doesn't disclose any additional behavioral traits such as side effects or required permissions. This is comparable to the get_calls example, scoring a 3.

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 succinct sentence that front-loads the purpose and includes one key usage instruction. There is zero filler or redundant content.

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 tool's simplicity, the description covers the core purpose and reproduction guidance, but the lack of parameter details and the type mismatch for 'conversation' create ambiguity. An agent would struggle to populate the parameters correctly without additional context.

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%, so the description must compensate. It does mention the 'conversation' parameter and its purpose, but it refers to it as an 'array' while the schema defines it as a string with default '[]'. It does not explain 'message' or 'context' parameters, leaving meaning unclear. This is insufficient given the 0% schema coverage.

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: 'Report a bug, missing feature, or send feedback.' It uses a specific verb ('Report') and resource ('bug, missing feature, feedback'), and the sibling tools (e.g., authenticate, marketplace, tribunal) are distinctly different, making the purpose unambiguous.

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 clear context for when to use the tool (reporting bugs/features/feedback) and adds a usage instruction ('Include the conversation array with recent messages for reproduction'). It doesn't explicitly mention alternatives or exclusions, but the sibling tools are so different that the context is sufficient.

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