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

Annotations already convey mutation safety (readOnly=false, destructive=false) and idempotency, so the description's main addition is the requirement to include conversation context. It doesn't disclose side effects, duplicate handling, or authentication needs, but the annotations cover the core risk profile.

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 tight sentences: the first states the action and scope, the second provides a key usage hint. No filler or repeated schema information.

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 tool with three parameters and no output schema, the description covers the primary purpose and one important parameter. However, it omits clarification of 'message' and 'context', so the tool is not fully self-contained for an agent without additional inference.

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. It only clarifies the 'conversation' parameter and leaves 'context' completely unexplained; 'message' is implicit but not formally described. This is inadequate coverage for a schema with zero descriptions.

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 starts with a specific verb ('Report') plus the resources (bug, missing feature, feedback), and clearly distinguishes this from sibling tools like show_version or authenticate. It concisely defines what the tool accomplishes.

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 enumerates three explicit use cases and adds practical guidance to include the conversation array for reproduction. While it doesn't mention when not to use it or point to alternatives, the stated scope gives clear context for selection.

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