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

Annotations already communicate non-read-only, non-destructive, and idempotent behavior. The description adds the useful detail that the conversation array is needed for reproduction, but it does not describe what happens after reporting or any return/confirmation behavior.

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 two concise sentences with front-loaded action and no filler. Every sentence contributes either purpose or usage guidance.

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?

Given the simple 3-parameter tool and available annotations, the description is adequate but has gaps: the 'context' parameter is unexplained, the expected return/confirmation behavior is absent, and the conversation parameter's string format is not clarified. It is a minimal viable description, not a complete one.

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 description clarifies the purpose of the conversation parameter ('recent messages for reproduction'), but schema coverage is 0% and the required 'message' and optional 'context' parameters are not explained. It also calls conversation an 'array' while the schema expects a string, which is a format ambiguity.

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 action ('Report') and the resource ('bug, missing feature, or send feedback'), making the tool's purpose unambiguous. It is easily distinguished from the unrelated sibling tools such as authenticate, connect, and show_version.

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 provides clear context for when to use the tool: for bugs, missing features, or general feedback. It does not explicitly list exclusions or alternative tools, but the use cases are specific enough and the siblings are not plausible alternatives.

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