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

The description mentions that the conversation array should be included, implying the tool uses it for reproduction. However, it does not disclose side effects (e.g., ticket creation) or address the idempotentHint annotation. The annotations already provide readOnly and destructive flags, so the description adds limited behavioral context beyond input usage.

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 a single sentence, front-loads the purpose, and includes one essential usage instruction. No fluff or repetition.

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 and no output schema, the description covers the basic action and the key input requirement. However, it omits return expectations and misrepresents the conversation field type, leaving some gaps for a complete 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?

Schema description coverage is 0%; the description attempts to explain the 'conversation' parameter but calls it an 'array' while the schema defines it as a string (likely JSON). It does not explain 'message' (which is required) or 'context' at all, so the semantic burden is largely unmet.

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 uses a specific verb 'report' and clearly identifies the resource as a bug, missing feature, or feedback. This distinguishes it from sibling tools like authenticate or toolkit_info, none of which handle user feedback.

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 gives context for use: reporting issues or sending feedback. It also instructs to include the conversation array for reproduction, which is a useful how-to. However, it doesn't explicitly exclude alternative tools, but no siblings overlap.

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