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

Annotations correctly declare readOnlyHint=false, destructiveHint=false, and idempotentHint=true, so the agent already knows this is a non-destructive but non-read-only reporting action. The description adds that the conversation array should contain recent messages for reproduction, which is useful behavioral context, but it does not disclose what happens after the report is submitted (e.g., acknowledgment, tracking number) beyond what annotations imply.

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 exceptionally concise: two sentences, immediately placing the core purpose first and a specific usage tip second. No filler, repetition, or redundant information from the schema is present.

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 relatively simple with 3 parameters and no output schema, so complete documentation would be short. The description provides the core purpose and one key parameter detail (conversation for reproduction), but it omits the function of the 'context' parameter and gives no sense of what the user can expect upon completion (e.g., a response or success indicator).

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 parameter explanations. It explicitly explains the 'conversation' parameter's purpose ('recent messages for reproduction'), but gives no explanation for 'context' or 'message' beyond the obvious. This is insufficient for full compensation, especially since 'context' is an optional parameter with a subtle meaning.

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 begins with the specific verb 'Report' and names explicit objects: 'a bug, missing feature, or send feedback', clearly identifying the tool's purpose. It is also distinct from all sibling tools (authenticate, marketplace, show_version, etc.), which belong to different functional domains.

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 explicitly states when to use the tool ('Report a bug, missing feature, or send feedback') and provides a specific usage instruction ('Include the conversation array with recent messages for reproduction'). It does not explicitly mention that other tools are not appropriate, but the sibling tools are so clearly unrelated that no exclusion is necessary.

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