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

Annotations already provide readOnlyHint=false, destructiveHint=false, and idempotentHint=true, covering the safety profile. The description adds the context that a conversation array is needed for reproduction, which is useful but not a deep behavioral disclosure. It does not contradict annotations, but also does not add significant behavioral context beyond what is already structured.

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 only two sentences, front-loaded with the purpose, and gives one key directive. There is zero fluff; every word earns its place. It is appropriately sized for a simple tool.

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 3 parameters, no output schema, and no nested objects, the description covers the core purpose and a critical usage detail (conversation array). It doesn't explain return behavior, but with no output schema that is not required. It could mention context, but overall it is complete enough for a simple reporting tool.

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?

With schema description coverage at 0%, the description must compensate. It explicitly mentions the 'conversation' parameter and implies the 'message' parameter (the bug/feature content), but does not explain the 'context' parameter at all. This partial clarification helps but leaves a gap for one of the three parameters.

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+resource combo that distinguishes it from sibling tools like authenticate or connect, which have entirely different functions. No ambiguity exists about what this tool does.

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?

It explicitly instructs users to 'Include the conversation array with recent messages for reproduction,' which is a practical usage guideline. While it doesn't name alternative tools or state when not to use it, the context implies this is the go-to for bug/feedback reporting, and the conversation array guidance is valuable and actionable.

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