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

Annotations already indicate readOnlyHint=false, destructiveHint=false, and idempotentHint=true, so the safety profile is known. The description adds value by noting the need for conversation data, but it does not elaborate on side effects, response handling, or privacy concerns. With annotations present, the additional disclosure is adequate but minimal.

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, front-loaded with the purpose, and contains no extraneous words. Every sentence contributes meaning, and the structure is ideal for quick comprehension.

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 (3 parameters, no output schema), and the description, combined with annotations, provides a basic understanding. However, the lack of explanation for the 'context' parameter and no mention of what happens after submission leaves some gaps. Overall, it is minimally complete for a straightforward reporting tool but could be more thorough.

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 meanings. It explicitly explains the 'conversation' parameter as an array with recent messages for reproduction, but does not explain 'message' (though its role as the report content is implied) or 'context' (which remains vague). Thus, only one of three parameters is clearly clarified, leaving a significant gap.

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 a specific verb ('Report') and resource ('a bug, missing feature, or feedback'), making the tool's purpose unambiguous. It distinguishes itself from siblings like authenticate or show_version, which serve entirely 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 explicit instruction to include the conversation array for reproduction, which is a concrete usage guideline. While it does not mention alternatives or exclusions, the sibling tools are clearly unrelated (auth, version, marketplace), so there is no ambiguity about when to use this tool.

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