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

The description adds behavioral context beyond annotations by specifying that the conversation array should be included for reproduction. Annotations already indicate this is a non-read-only operation (readOnlyHint=false) and idempotent, so no contradiction. It doesn't describe post-submission behavior, but that is not critical for a bug-reporting tool.

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 concise sentences, front-loaded with the core purpose and then a key usage instruction. Every word adds value; no fluff or repetition of schema fields.

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?

Given the tool's simplicity and the presence of annotations, the description covers essential aspects: what it does and what to include. Without an output schema, it doesn't describe return values, but that is not necessary for correct invocation. It is complete enough for an agent to select and call this tool appropriately.

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?

With schema coverage at 0%, the description partially compensates by explaining 'message' (the report content) and 'conversation' (to include for reproduction). However, it does not explain the 'context' parameter, and it calls 'conversation' an array while the schema defines it as a string, which could cause minor confusion.

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 tool's purpose with a specific verb ('Report') and resource ('bug, missing feature, or feedback'). It also provides a concrete instruction on what to include (conversation array), making it unmistakable and distinct from sibling tools that deal with authentication, marketplace, or version info.

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 when to use the tool: whenever the user needs to report a bug, missing feature, or send feedback. It also gives usage guidance by instructing to include the conversation array for reproduction. However, it does not explicitly mention when not to use it or alternative tools, though siblings are clearly unrelated.

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