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

Annotations already indicate idempotentHint=true, readOnlyHint=false, and destructiveHint=false. The description adds a behavioral instruction to 'Include the conversation array with recent messages for reproduction,' which is useful context but doesn't disclose other side effects. Since annotations cover the basic safety profile, this is adequate but not rich.

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 very concise—two sentences—and front-loaded with the primary purpose. The second sentence adds a necessary instruction. Every word contributes to understanding the tool, with no fluff or repetition.

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 flat parameters, no output schema), and annotations are provided. The description covers the core action and the key reproduction requirement, but omits parameter explanations for 'message' and 'context'. This is a noticeable gap, but the tool's simplicity and the annotation coverage keep it from being severely incomplete.

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 description coverage is 0%, so the description must compensate for parameter explanations. It explains only the 'conversation' parameter (describing it as an array for reproduction) but leaves 'message' and 'context' unaddressed. 'message' is required, and 'context' has a default but no elucidation. This partial explanation is insufficient given zero schema-level 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 clearly states the tool's purpose: 'Report a bug, missing feature, or send feedback.' This is a specific verb and resource, and it's distinct from sibling tools like authenticate, connect, or marketplace. It also adds a concrete instruction about including the conversation array, which reinforces the purpose.

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 implies when to use the tool ('if you have a bug, missing feature, or feedback'), which provides clear context. It doesn't explicitly mention exclusions or alternatives, but none of the sibling tools serve the same purpose, so no differentiation is needed. This falls between implied and explicit guidance.

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