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

Annotations already declare idempotentHint=true and destructiveHint=false, so the description isn't required to restate these. It adds value by instructing users to include the conversation array for reproduction, but it doesn't disclose side effects (e.g., sending data externally, creating a ticket) or what happens after submission. This is moderate transparency beyond 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 a single sentence that immediately states the tool's purpose and includes one critical usage note. Every word earns its place; there is no fluff 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?

The description offers a general purpose and one usage hint, but with three parameters and no output schema, it lacks detail on parameter roles and expected behavior. It is sufficient for a simple tool, yet gaps remain, particularly around the 'context' parameter and what constitutes a valid 'message'.

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 input schema has 0% description coverage, so the description must compensate for parameter meanings. It explicitly mentions 'conversation array' and 'message' but does not clarify the 'context' parameter or the expected format of 'message.' The description fails to fully explain all three parameters, leaving significant ambiguity.

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 plus resource: 'Report a bug, missing feature, or send feedback.' This distinguishes it from sibling tools like authenticate, connect, or marketplace, which serve entirely different functions.

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 provides clear usage context by telling the user to include the conversation array with recent messages for reproduction. While it doesn't explicitly name alternatives or exclusions, sibling tools are sufficiently different that no ambiguity exists. It effectively communicates the intended use case.

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