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

Annotations indicate idempotentHint=true and destructiveHint=false, which are not contradicted by the description. The description adds that the tool is for reporting feedback, implying a non-destructive action. It does not disclose backend behavior (e.g., ticket creation), but annotations already cover idempotency and safety.

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 extremely concise, consisting of two sentences: the first states the purpose, and the second provides key guidance. There is no redundant information, and every word is useful.

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 tool with 3 parameters, the description covers the core purpose and one parameter's usage. However, it omits explanation of the 'message' and 'context' parameters, and since there is no output schema, the return value is not hinted at. It is adequate but not fully complete.

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 only partially explains the 'conversation' parameter ('Include the conversation array with recent messages for reproduction'), but fails to explain the required 'message' parameter and the optional 'context' parameter. This leaves significant ambiguity.

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 specific verbs and resources, and it distinguishes itself from sibling tools which are primarily business-specific operations (e.g., contaazul_*).

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 provides explicit guidance to 'Include the conversation array with recent messages for reproduction,' which helps users understand when and how to use the tool. However, it does not explicitly state when not to use this tool versus alternatives, but context makes it clear.

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