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

Annotations already declare idempotentHint=true and destructiveHint=false, covering the safety profile. The description adds minimal behavioral context (e.g., that conversation data is used for reproduction), but does not elaborate on side effects or post-submission actions. This is acceptable given the annotations, but not enriched.

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 concise: two sentences, first stating the purpose, second giving a key usage instruction. No redundant words or fluff.

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 tool with three params and no output schema, the description provides the high-level purpose and a critical detail (conversation inclusion) but omits clarification of the 'message' and 'context' fields. It doesn't mention that 'message' is required or what 'context' represents, leaving gaps. Adequate but not fully complete.

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 mentions the 'conversation array' and explains its purpose ('with recent messages for reproduction'), adding meaning beyond the schema's bare string type and default. However, it fails to explain the 'message' (required) or 'context' parameters, leaving them ambiguous. Partial coverage.

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.' It uses a specific verb (report) and identifies the target (bug/feedback), and none of the sibling tools serve this function, making it highly distinguishable.

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 implicitly indicates when to use this tool (for reporting bugs/features/feedback) and provides a specific instruction: 'Include the conversation array with recent messages for reproduction.' While it doesn't explicitly contrast with alternatives, it gives clear context for appropriate usage.

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