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

Annotations cover idempotency and destructive hints, but the description adds no further clarification on side effects (e.g., ticket creation, notifications). It only mentions including conversation data, which is more of a parameter hint than behavioral disclosure.

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 concise and well-structured, using two clear sentences. It avoids unnecessary details and effectively communicates the core purpose and a key usage hint.

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 is simple, but the description lacks details about the outcome (e.g., what happens after reporting) and does not fully specify the expected format of the conversation parameter. While it covers the basics, it is not complete for a full understanding of the tool's behavior.

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 zero descriptions, and the description partially clarifies the conversation parameter by mentioning 'conversation array' for reproduction. However, it does not explain the 'context' parameter or the structure of 'conversation', leaving gaps in parameter understanding.

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 sending feedback. This is distinct from sibling tools like authentication or marketplace, making its function 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?

The description implies when to use the tool (e.g., when a bug is encountered) but does not explicitly differentiate it from alternatives or state when not to use it. The instruction to include conversation data provides some usage guidance, but it lacks explicit selection criteria.

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