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

Annotations already flag idempotentHint=true and destructiveHint=false, so the description does not need to repeat these. It adds a usage note about including the conversation array for reproduction, but does not disclose any side effects or post-action behavior. Given the annotation coverage, this is adequate but not rich.

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 short sentences, front-loaded with the core purpose and followed by a single actionable instruction. No wasted words, ideal for quick scanning.

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 with no output schema and straightforward parameters, the description covers the core action and one parameter nuance. However, it omits guidance on what to include in the 'message' field and does not explain the meaning of 'context'. This is a notable gap for an agent that must construct valid payloads, so completeness is below par.

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 adds meaning only to the 'conversation' parameter by specifying it should contain recent messages for reproduction, but provides no guidance on the required 'message' parameter or the optional 'context'. This partial coverage leaves significant gaps.

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 it reports a bug, missing feature, or sends feedback. This specific verb+resource distinguishes it from sibling tools like authenticate or show_version, leaving no ambiguity about its purpose.

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 using the tool when encountering issues or providing feedback, but does not explicitly state when not to use it or mention alternatives. It offers some guidance on including a conversation array, but lacks explicit exclusions or comparison with other tools.

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