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

Annotations indicate idempotentHint=true and destructiveHint=false, suggesting a safe, non-destructive operation. The description adds that it requires a conversation array for reproduction, which is useful behavioral context. It doesn't mention response behavior or side effects, but given the annotations, the description adds some extra value without contradiction.

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 a single, focused sentence that covers the core purpose and the key parameter guidance. It is front-loaded with the action and includes the critical instruction about the conversation array. No redundant words.

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, no output schema, and one required field. The description provides enough context for basic use and the key reproduction detail. It lacks full parameter coverage (context is unexplained), but the core usage is clear for a feedback tool. Given the straightforward nature, the description is sufficiently complete for an agent to select and 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?

The schema has 0% description coverage, so the description must compensate. It mentions the 'conversation' parameter ('Include the conversation array with recent messages for reproduction') and indirectly references the 'message' parameter as the main content. However, it doesn't explain the 'context' parameter, which is included in the schema but not addressed in the description. Since the description covers two of three parameters, it provides partial compensation.

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 states the tool's purpose: 'Report a bug, missing feature, or send feedback.' This is a clear verb (report/send) with specific resource types (bug, missing feature, feedback), and it implies a single action. It doesn't explicitly distinguish from siblings, but the sibling list doesn't include similar feedback tools (e.g., 'authenticate', 'connect', 'marketplace'), so it stands out adequately.

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 says when to use it (when reporting a bug or sending feedback) and hints at what to include (conversation array with messages). However, it doesn't provide explicit exclusions or alternative tool references. There is no guidance on when not to use it, but given the simple nature and no obvious overlap, this is acceptable.

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