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

Annotations already declare readOnlyHint=false and destructiveHint=false, covering safety expectations. The description adds the behavioral nuance that the conversation array is used for reproduction, but doesn't disclose side effects like ticket creation or data storage. With annotations present, this is acceptable but not rich.

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, front-loaded sentence that conveys purpose and a critical usage instruction. No filler or redundant content.

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 covers the core action and a key usage detail (conversation for reproduction). It's missing explanation of the 'context' parameter, but overall the tool is straightforward and the provided info is sufficient for most use cases.

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 explains the purpose of the 'conversation' parameter ('Include the conversation array with recent messages for reproduction') and implies 'message' is the report text. However, 'context' remains unexplained, and the overall parameter guidance is minimal.

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 'Report a bug, missing feature, or send feedback'—a specific verb and resource that distinguishes this from siblings like authenticate or marketplace. The purpose is immediate and unambiguous.

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?

It provides clear context—this is the tool for bug/feature/feedback reports. It also instructs to include the conversation array for reproduction. However, it doesn't explicitly contrast with alternatives, but no sibling tool serves a similar purpose, so this is sufficient.

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