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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=true. The description adds the key behavioral context that the conversation array is needed for reproduction, which is useful beyond annotations. However, it does not explain side effects (e.g., whether a ticket is created) or any auth requirements, so it doesn't go beyond a minimum viable level.

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 sentences, front-loaded with the purpose, and the second sentence adds a critical usage detail. Every word earns its place; no fluff 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?

For a simple report tool with 3 params and no output schema, the description covers the core purpose and the most important parameter (conversation). But given zero schema descriptions, the 'context' parameter is left unexplained, and there is no indication of what happens after submission (e.g., confirmation, response). This is adequate but with clear gaps.

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 provides some meaning for the 'conversation' parameter ('Include the conversation array with recent messages for reproduction.') and implied meaning for 'message' as the bug text. However, it does not explain the 'context' parameter at all, leaving a meaningful gap given the lack of schema 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 function: 'Report a bug, missing feature, or send feedback.' The verb 'report' plus the specific resource (bug/feature/feedback) makes the purpose explicit. This also distinguishes it from sibling tools like authenticate, show_version, and tribunal process consultation.

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 gives direct usage guidance: 'Include the conversation array with recent messages for reproduction.' This tells the agent what to do when invoking the tool. It does not explicitly mention when not to use it or alternatives, but the context is clear for a feedback/reporting operation.

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