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

Annotations indicate idempotentHint: truecluster, but the description doesn't conflict. It adds a useful instruction about including conversation data for reproduction, which gives behavioral context. However, it doesn't disclose any side effects or authorization needs beyond that.

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 directly states the tool's purpose and one key usage instruction (include conversation). It's not overly verbose, but lacks structured parameter explanation.

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 gives purpose and reproduction guidance, but doesn't specify when to use vs. alternatives or any limitations. With annotations stating idempotent, it's clear it's not destructive, but could benefit from more context on expected outcomes.

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's purpose but not 'context'. The schema has no descriptions, and the description calls 'conversation' an array while schema says string, which is slightly ambiguous. 'message' is self-explanatory. 'context' is vague.

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 names specific resources (bug, feature, feedback) and the action (report/send), which clearly differentiates it from sibling tools like 'authenticate' or 'connect'.

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 context on when to use it (for reporting issues) and explicitly instructs to include the conversation array for reproduction. However, it does not mention situations where it should not be used or how it compares to alternatives, but the context is clear enough.

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