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

Annotations already convey idempotentHint true and destructiveHint false, lowering the burden on the description. The description adds the behavioral expectation that conversation history is needed for reproduction, which is helpful context. Yet it does not disclose side effects, validation, or what happens after submission, so it only partially enriches the annotations.

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 sentences, front-loaded with the purpose, followed by a succinct usage tip. Every word earns its place with no redundancy or filler.

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 3-parameter tool with no output schema, the description leaves critical gaps: it does not specify that 'message' is required, misdescribes 'conversation' as an array, and ignores 'context'. While the schema can fill some gaps, the description should compensate for the 0% schema coverage but does not, leaving the agent uncertain about required inputs and types.

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 for all parameters. It mentions only the 'conversation' param, but describes it as an 'array' while the schema defines it as a string, which is misleading. The required 'message' param is only implied, and 'context' is entirely omitted. This fails to clarify parameter formats and purpose.

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: 'Report a bug, missing feature, or send feedback.' This is a specific verb-resource pairing and distinguishes it from sibling tools like 'connect' or 'authenticate' which serve different purposes. No ambiguity.

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 a clear usage instruction: 'Include the conversation array with recent messages for reproduction.' It implies the tool is for reporting issues or feedback, and no sibling tool offers this capability, so when to use it is evident. However, it lacks explicit exclusions or alternative recommendations.

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