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

Annotations declare idempotentHint true and readOnlyHint false, but the description adds no behavioral context about side effects (e.g., data transmission, network calls, or what happens after reporting). The mention of including conversation for reproduction hints at required inputs but does not clarify the tool's external impact or failure modes. No contradiction, but minimal additional transparency.

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 concise sentences deliver the core purpose and a key parameter hint without unnecessary verbiage. Every word adds value, and the most critical information is front-loaded.

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 reporting tool with 3 parameters and no output schema, the description is adequate but misses opportunities to mention return values or side effects. It provides enough to understand the basic function but lacks detail on post-submission behavior or error handling. Given the low complexity, this is acceptable yet improvable.

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 that 'conversation' should contain recent messages for reproduction, adding some meaning, but leaves 'context' and 'message' unexplained. No formats, defaults, or examples are provided, leaving the agent to guess their purpose beyond generic naming.

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 action ('Report a bug, missing feature, or send feedback') with a specific verb and resource. Sibling tool names (authenticate, marketplace, etc.) are unrelated, so there is no ambiguity. The purpose is immediately understandable.

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?

No explicit guidance on when to use this tool versus alternatives. The instruction to 'Include the conversation array with recent messages' is a peripheral usage hint but does not address selection criteria, exclusions, or contrast with sibling tools. There is no 'when-not-to-use' guidance, leaving the agent to infer usage from the name alone.

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