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

The annotations provide idempotentHint=true and destructiveHint=false, but the description does not elaborate on side effects or outcomes. It does give a behavioral instruction to include the conversation array, which adds some transparency, but it does not discuss what happens after submission (e.g., ticket creation, confirmation).

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, consisting of two sentences that are directly to the point. It avoids unnecessary details and is well-structured for quick comprehension.

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 provides enough context for basic usage but lacks information about return values or outcomes (since there is no output schema). It also does not mention error handling or asynchronous behavior, making the overall context incomplete for advanced scenarios.

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 description explains the 'conversation' parameter by stating it should contain recent messages for reproduction, adding value beyond the schema. However, it does not clarify the 'context' parameter or the exact format of 'message', leaving some parameters underdescribed.

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 function: reporting bugs, missing features, or feedback. It also specifies the need to include the conversation array, making the purpose distinct from sibling tools like authentication or connection tools.

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 implicitly indicates when to use this tool (when reporting an issue) and provides instructions on including the conversation for reproduction. However, it does not explicitly mention alternatives or edge cases, but given the sibling tools are unrelated, the usage context is clear.

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