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

Annotations already convey non-destructive and idempotent behavior. The description adds contextual guidance about what should be included for reproduction, but it does not disclose any deeper behavioral outcomes (e.g., ticket creation, server-side effects, response behavior). It provides some value beyond annotations but not rich detail.

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?

Two sentences, immediately front-loaded with the tool's purpose and followed by a single actionable instruction. No 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?

For a simple, low-parameter tool with no output schema, the description covers the core intent, use cases, and a key reproduction instruction. It is reasonably complete, though the `context` parameter remains underspecified and no return behavior is mentioned.

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?

With 0% schema description coverage, the description bears the burden of explaining parameters. It clarifies the `conversation` parameter by describing it as an array of recent messages, and `message` is implied as the report content. However, the `context` parameter is left unexplained, and the description calls `conversation` an 'array' while the schema declares it as a string type, which could introduce ambiguity.

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 identifies the tool's purpose with a specific verb and resource: 'Report a bug, missing feature, or send feedback.' This is unambiguous and distinct from the sibling tools, which are unrelated to bug 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 states the applicable contexts ('bug, missing feature, or feedback') and tells the agent to 'Include the conversation array with recent messages for reproduction.' It lacks an explicit when-not-to-use or alternative-tool reference, but no sibling is an obvious substitute.

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