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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=true, which covers safety and idempotency. The description adds that the conversation should be included for reproduction, which is useful for understanding the tool's purpose. It does not disclose any additional side effects or behaviors, so the description adds limited value beyond 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 description is extremely concise, consisting of two short sentences. It is front-loaded with the core purpose and immediately provides the key usage instruction. No fluff or unnecessary details.

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 simple (a bug/feedback reporter) with no output schema alert. The description covers the primary purpose and mentions the conversation inclusion. However, it does not explain what happens after submission, nor does it fully disambiguate the three parameters. Given the lack of parameter explanations, the description is minimally complete but not thorough.

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 for parameter understanding. It only explains the 'conversation' parameter ('include the conversation array'), but does not clarify 'message' or 'context'. The 'message' parameter is required, yet its purpose is not explained. With only one of three parameters addressed, the description is insufficient.

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 purpose: 'Report a bug, missing feature, or send feedback.' It uses a specific verb ('report') and identifies the resource (bug/missing feature/feedback). It is distinct from sibling tools like authenticate, connect, and marketplace, none of which relate to bug reporting.

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 provides clear usage context: it's for reporting bugs, missing features, or feedback. It also instructs to include the conversation array for reproduction, which is useful preparation. However, it does not explicitly state when to use this tool over alternatives or when not to use it, though the sibling tools are clearly unrelated.

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