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

The description mentions needing the conversation for reproduction but does not disclose behavior such as side effects, permissions required, or what actions the tool takes (e.g., creating a report, sending feedback). The annotations (readOnlyHint, destructiveHint) are default and not contradicted, but the description adds little transparency about the tool's execution or consequences.

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, consisting of two sentences, with no redundant information. It directly states the action and provides a key instruction, making it easy to read and understand without unnecessary verbosity.

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?

Given the schema and the description, important context is missing. The description only covers one of three parameters, and that explanation conflicts with the schema type. There is no mention of return values, expected outcomes, or any additional behavioral context. The tool feels incomplete for a user to effectively use without further clarification.

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 schema defines three parameters (context, message, conversation) but the description only explains conversation, and even then incorrectly calls it an 'array' while the schema type is 'string'. There is no guidance on the purpose or format of 'context' or 'message', and the type contradiction undermines clarity. This is a significant gap that could lead to misuse.

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 a specific verb ('report') and clearly distinguishes the resource from sibling tools like authenticate or connect, making it easy to identify when this tool is appropriate.

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 direct usage instruction ('Include the conversation array with recent messages for reproduction') but does not explicitly state when to use this tool versus alternatives. However, since none of the sibling tools handle bug reporting, the context is somewhat implied. The instruction itself is helpful but lacks broader usage context.

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