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

Annotations already indicate idempotentHint=true and destructiveHint=false, conveying safety traits. The description adds no behavioral context beyond these annotations, such as whether the report creates a ticket or triggers notifications.

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 succinct with two sentences. The first delivers purpose, the second provides actionable instruction. No unnecessary words or repetition.

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 feedback tool with 3 parameters and no output schema, the description covers the basic intent and a key usage tip. However, it omits what happens after reporting (e.g., confirmation, ticket creation) and any limits or side effects.

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?

The schema has 0% description coverage, so the burden falls on the free-text description. It clarifies the 'conversation' parameter's purpose ('recent messages for reproduction') but does not explain 'context' or 'message' parameters in any detail.

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: reporting a bug, missing feature, or feedback. It uses a specific verb ('Report') and identifies resources. While it distinguishes from financial siblings by category, it does not explicitly differentiate from other non-financial tools.

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 instructs users to include the conversation array, which is a useful guideline for proper reproduction. However, it lacks guidance on when to use this tool versus alternatives (e.g., when not to report bugs) and does not mention any prerequisites.

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