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

Annotations include idempotentHint=true compact with the description's implication of submitting a report, which is not a destructive or read-only operation. The description adds context about reproduction data, which is useful. It does not fully detail side effects, but annotations cover the main behavioral hints, so this is adequate beyond the annotation baseline.

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-loads the core purpose, and adds the one important detail (conversation array) without unnecessary fluff. Perfectly concise.

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 relatively simple, but with 3 parameters and no output schema, the description does not fully explain all parameters or return values. It provides the essential usage context but lacks detail on what happens after reporting (e.g., response format). This is a moderate gap, so a 3 is appropriate.

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. However, the description only mentions the conversation array, while the schema has three parameters. It does not explain 'context' or the format of 'conversation' (which is a string but likely JSON). This is a minimal addition beyond the schema, earning a 3.

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 that the tool reports bugs, missing features, or feedback, with specific mention of including a conversation array. It is distinguishable from siblings like authenticate and marketplace, which have different purposes.

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 context on when to use the tool (when encountering a bug, missing feature, or wanting to send feedback) and what to include (conversation array). It does not explicitly mention when not to use it or list alternatives, but the purpose is specific enough to guide usage.

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