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

Annotations indicate idempotent and non-destructive, and the description adds that the conversation array is needed for reproduction, implying data is sent for debugging. However, it does not disclose side effects, such as ticket creation or data storage. With annotations covering safety profile, the description provides moderate additional context but lacks depth.

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 two concise sentences with no redundant information. It front-loads the purpose and includes a key instruction about the conversation parameter, making it efficient and well-structured.

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 tool with 3 parameters and no output schema, the description is too sparse. It mentions only one parameter and omits guidance on the others. The tool is simple, but the description fails to cover essential parameter semantics, leaving gaps in the agent's understanding.

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 only references the conversation parameter, but does not explain the required message field or the optional context field. Schema description coverage is 0%, and the description fails to compensate for the missing parameter documentation, leaving the agent with limited understanding of how to construct valid inputs.

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: report a bug, missing feature, or send feedback. It uses a specific verb ('report') with explicit resource types, and it is distinct from sibling tools like authenticate, connect, and marketplace, which focus on other 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 gives a clear purpose but provides no explicit guidance on when to use this tool versus alternatives. It does not mention exclusions or scenarios where another tool would be more appropriate, so usage context is implied rather than stated.

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