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

Annotations already provide idempotentHint and indicate non-read-only/non-destructive behavior. The description adds the instruction to include conversation but does not explain side effects (e.g., ticket creation, notification). Given the annotations, this is adequate but not enriching.

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 concise sentences that clearly convey the purpose and a specific actionable instruction. No unnecessary 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?

The description fails to cover all parameters and does not mention any expected outcome or error handling. While no output schema exists, the tool still lacks important context for a complete understanding.

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 description only explains the purpose of the 'conversation' parameter ('for reproduction'). It does not clarify 'context' or 'message.' Since schema descriptions are absent, this leaves user confusion about required inputs.

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?

Clearly states the action ('Report') and the object ('bug, missing feature, or send feedback'). Distinguishes itself from siblings like authenticate or show_version by describing a distinct 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?

Implies usage when an issue is encountered or feedback is needed, and instructs to include the conversation array for reproduction. Does not explicitly mention when to avoid using it, but the context is clear enough.

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