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

Annotations include idempotentHint: truechers and readOnlyHint: false, which suggest the operation may have side effects (like creating a report) but is idempotent (repeated calls have no additional effect). The description does not explicitly mention side effects or idempotency, but it does add context about including the conversation array for reproduction, which is beyond annotations. However, it does not clarify what happens after reporting (e.g., how the report is processed) or any side effects like creating a ticket. Given annotations cover some safety aspects, but description could add more behavioral details.

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, and front-loads the purpose. It provides essential information without excessive detail. It earns a high score for brevity, but loses a point because it could be slightly more structured (e.g., breaking down what to include for different report types).

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 tool has 3 parameters with no output schema and limited annotations, the description provides enough to understand the main input (message) and the reproduction aid (conversation). However, it lacks details on the 'context' parameter and does not describe expected outcomes or response behavior. For a simple reporting tool, this might be acceptable, but it could be more complete by clarifying parameter usage and what happens after submission.

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 missing parameter explanations. The description mentions 'conversation array' and 'recent messages' but does not elaborate on 'message' or 'context' parameters. The schema shows 'message' is required, 'context' defaults to empty, and 'conversation' is a string that likely represents the array. The description adds some meaning for 'conversation' but not for 'message' or 'context'. Since it partially compensates but not fully, a score of 3 is appropriate.

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: to report a bug, missing feature, or send feedback. It distinguishes itself from siblings by mentioning the conversation array for reproduction, which is unique among the listed tools. However, it does not explicitly differentiate from all sibling tools, but the verb 'report' and specific use case make it clear.

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 implies when to use the tool: when reporting a bug or feedback. It does not provide explicit when-not-to-use guidance or mention alternatives, but the context signals show sibling tools like 'marketplace' or 'show_version' are unrelated, so the purpose is clear. 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.