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

Annotations already indicate readOnlyHint=false and destructiveHint=false, setting expectations for side effects. The description adds useful guidance about including conversation history for reproduction, which complements the annotations without contradiction.

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?

Two short sentences deliver the core purpose and a key usage hint without verbosity. Every word earns its place.

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 simple tool (3 string params, no enums, no nested objects), the description covers the primary use case and one critical detail (conversation array). It does not describe all params, but the tool's simplicity lowers the burden enough to be nearly 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?

Schema description coverage is 0%, so the description must compensate. It clarifies the 'conversation' parameter's purpose but does not explain 'message' or 'context.' Partial compensation, not comprehensive.

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?

Description uses a specific verb 'Report' and identifies distinct resources ('bug, missing feature, or send feedback'), making the tool's purpose immediately clear. It also stands apart from unrelated sibling tools like 'authenticate' 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?

Provides clear context on when to use (for bugs, feedback, missing features) and explicit instruction to include 'conversation array with recent messages for reproduction.' It doesn't mention alternatives or exclusions, but the sibling set is diverse enough that this isn't a major gap.

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