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

Annotations already indicate idempotentHint=true and destructiveHint=false. The description adds context that conversation data should be included for reproduction, implying that the report will be used for debugging. It does not elaborate on side effects like data transmission or whether a confirmation/ticket is returned, but the annotation coverage lowers the burden. It does not contradict the annotations.

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 entire description is two sentences. It opens with the primary purpose and follows with a specific usage requirement. No filler or redundant details; every word contributes.

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 tool is relatively simple with three parameters and no output schema. The description covers the main scenario (reporting an issue), identifies the required message field, and provides guidance on the conversation field. It doesn't mention return values or confirmations, but that's not critical for a bug-report tool. Annotations add safety context, making it reasonably complete.

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 schema has 0% description coverage, so the description must compensate. It explicitly instructs to include the 'conversation' parameter with recent messages, giving it purpose. The 'message' parameter is implicitly described as the text of the bug/feedback. 'context' is not explained, but its name and default suggest it's optional contextual data. Overall, partial compensation for a low-coverage schema.

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 specifies the tool's function with a clear verb ('Report') and resource ('a bug, missing feature, or send feedback'). It distinguishes this tool from siblings like authenticate or show_version, none of which handle bug reporting. It also hints at the required parameter (message) as the content of the report.

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 clearly identifies when to use the tool: when there's a bug, missing feature, or feedback to submit. It does not explicitly mention alternatives or exclusions, but the sibling tools are unrelated, so the context is sufficient. However, it lacks explicit guidance on when not to use it, such as for general queries or non-technical issues.

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