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

Annotations already declare readOnlyHint=false and idempotentHint=true, indicating it's a write operation that is safe to retry. The description adds the expectation that a conversation array is needed for reproduction, which is useful behavioral context. However, it does not disclose other side effects, authentication requirements, or what happens on the server, so the added transparency is limited.

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: the first states the purpose, the second adds a crucial usage instruction. It is front-loaded, concise, and every sentence earns its place with no redundancy.

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 reporting tool with three parameters (one required) and no output schema, the description adequately covers the essential behavior: what to report and how to include reproduction context. The idempotentHint annotation clarifies retry safety. It does not specify response behavior, but that is not critical for this tool type. Overall, it is complete enough for an agent to invoke it correctly.

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 coverage is 0%, so the description must compensate. It explains the 'conversation' parameter as containing recent messages for reproduction and implies 'message' is the content of the report. However, the 'context' parameter is left unexplained, and the description does not provide full syntax or format details, leaving some parameters under-defined.

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 resource (bug/feedback) and is distinct from sibling tools like authenticate, connect, and show_version, which serve different functions.

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 clear context for usage by instructing to 'Include the conversation array with recent messages for reproduction,' which tells the agent when this tool is appropriate (i.e., when there is a conversation to reproduce an issue). It does not explicitly name alternatives, but none exist among the siblings, so the guidance is adequate.

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