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

Annotations already declare idempotentHint: true, readOnlyHint: false, and destructiveHint: false, so the safety profile is known. The description adds the instruction to include the conversation array for reproduction, which is useful behavioral context, but it does not disclose what happens after submitting (e.g., ticket creation or external side effects). No contradictions with 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 description is only two sentences, with the first stating the purpose and the second giving a specific usage instruction. Every sentence earns its place, with no redundancy or fluff.

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 (3 params, no output schema), but the description could be more complete. It covers purpose and gives guidance for the 'conversation' parameter, but does not explain the required 'message' field or any return/behavior after reporting. This leaves some gaps, especially given the low schema documentation.

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 explains the 'conversation' parameter as the array for reproduction, but leaves 'message' (the required parameter) and 'context' largely implied. The required message is reasonably inferred from the tool's purpose, but not explicitly described.

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 uses a specific verb 'Report' and names the resource as 'a bug, missing feature, or feedback', which directly and unambiguously identifies the tool's purpose. This clearly distinguishes it from the sibling tools, all of which are unrelated (auth, marketplace, version info, etc.).

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 states what the tool is for ('Report a bug, missing feature, or send feedback'), providing enough context for when to use it. It does not explicitly mention when-not-to-use or list alternatives, but the sibling tools are so unrelated that no confusion is likely. This meets the 'clear context, no exclusions' level.

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