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

Annotations already cover readOnlyHint, destructiveHint, openWorldHint, and idempotentHint, so the description's burden is lower. It adds the key behavioral nuance that conversation history should be attached for reproduction. It does not disclose what happens after submission, but this is not safety-critical given the non-destructive, idempotent 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?

One sentence, no filler, and the purpose comes before the usage instruction. The description is tightly written and earns every word.

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 tool is simple: three parameters, no output schema, no nested objects. The description covers the core purpose and the reproduction requirement, but it omits what the message should contain, what context means, and what the agent should expect after reporting. It is adequate but has clear gaps.

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, but it only clarifies the conversation parameter ('recent messages for reproduction'). The required 'message' parameter and the 'context' parameter are left undocumented, and calling conversation an 'array' is slightly misleading since the schema declares it as a string with a '[]' default.

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 states a specific verb and resource: 'Report a bug, missing feature, or send feedback.' This clearly distinguishes the tool from the many operation-focused superlogica siblings and makes its purpose immediately obvious.

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 clear invocation use cases: bugs, missing features, and feedback. It also tells the agent to include the conversation array for reproduction. No sibling tool offers this function, so explicit exclusions are unnecessary, but they are not stated either.

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