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

Annotations already convey idempotentHint=true, readOnlyHint=false, and destructiveHint=false. The description adds the useful context that this tool is for reporting issues with reproduction data, but does not disclose additional behavioral traits such as authentication needs, rate limits, or what happens after submission. No contradiction 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 short sentences, front-loading the core purpose and including a critical usage note. Every word earns its place; there is no redundancy or filler.

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?

For a tool with 3 parameters (1 required), no output schema, and zero schema descriptions, the description provides the essential purpose and one key parameter hint. It falls short by not explaining the required message field or the optional context field, making the guidance incomplete but still minimally viable.

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 partially explains the conversation parameter ("Include the conversation array with recent messages for reproduction") but leaves the required message parameter and the context parameter unelaborated, forcing the agent to infer their meaning from the tool name alone.

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: "Report a bug, missing feature, or send feedback." The verb "report" and the resource types (bug, missing feature, feedback) are specific and distinct from sibling tools like authenticate, connect, and marketplace.

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 establishes a clear usage context: use this tool to submit bugs, feature requests, or feedback. It also gives a specific instruction to include the conversation array for reproduction, which helps the agent know what to provide. However, it does not explicitly name alternatives or describe when not to use the tool.

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