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

Annotations indicate idempotent and non-destructive behavior, and the description adds that the conversation array is for reproduction. However, it does not clarify side effects (e.g., whether the report is sent to a server) or any additional behavioral nuances, so transparency is moderate.

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, clear sentence with no redundant details. It is well-structured and easily understood.

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 tool's purpose and basic usage are covered, but the description lacks details about the expected format of the conversation array, the nature of the 'message' field, and any output or error handling. It is adequate but not comprehensive.

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 provides no descriptions for the three parameters. The description only mentions that the conversation array should contain recent messages, leaving 'message' and 'context' ambiguous. Parameter semantics are largely undocumented.

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 explicitly states the tool's purpose: reporting bugs, missing features, or sending feedback. It is distinct from all sibling tools (authenticate, connect, marketplace, etc.), which handle unrelated operations.

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 clearly indicates when to use the tool (for bug reports or feedback) and includes a specific instruction to include the conversation array for reproduction. It does not explicitly state when not to use it, but no alternative tool exists, so the guidance is sufficient.

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