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

The annotations already wire safety signals (readOnlyHint=false, destructiveHint=false, idempotentHint=true), so the bar is lower. The description adds minimal behavioral context—that conversation context is used for 'reproduction'—but doesn't disclose outcomes like confirmation behavior, auth expectations, or data persistence. No contradiction with annotations.

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 front-loaded with intent and groups its targets efficiently ('a bug, missing feature, or send feedback'). Both sentences earn their place, and the whole text is compact, though the helper instruction could arguably be structured as a parameter note.

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?

With only 3 string parameters, no nested objects, and no output schema, this is a simple tool that the description adequately scopes at a high level. However, it stops short of explaining message content expectations or post-submission behavior, leaving modest gaps for a mutation-like endpoint.

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%, placing the full burden on the description. Yet the text only references the 'conversation' parameter (for reproduction), leaving the required 'message' field and the 'context' field completely unexplained. This is a significant gap for the single required parameter.

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 uses a specific verb ('Report') and resource ('a bug, missing feature, or send feedback'), making the tool's purpose immediately clear. It distinguishes itself from the sibling tools (authenticate, connect, marketplace, etc.) which are all obviously different functions, though no alternatives are explicitly named.

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 instruction to 'Include the conversation array with recent messages for reproduction' implies procedural context but doesn't explicitly state when to use this instead of alternatives or list exclusions. Usage guidance is only implied through the reproduction hint, never stated as explicit conditions.

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