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

Annotations already provide readOnly/destructive/idempotent hints, so the bar is lower. The description adds that conversation data is used for reproduction, but it does not disclose what happens after reporting (e.g., confirmation, ticket/ID, or side effects of repeated submissions).

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 short and front-loaded, using two sentences effectively. The only flaw is the imprecise 'conversation array' wording, which introduces ambiguity.

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 simple with three parameters and no output schema, and the description conveys the overall purpose well. However, it is not fully self-sufficient because it does not clarify the required message field and misstates the conversation field type.

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 carries the full burden for parameter meaning. It mentions the conversation parameter but calls it an 'array' while the schema types it as a string; it also ignores the required 'message' parameter and the optional 'context' 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 clearly lists targets: bug, missing feature, or feedback. It is distinct from sibling tools like authenticate, show_version, and toolkit_info.

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 identifies concrete use cases (bug, missing feature, feedback) and instructs the agent to include conversation data for reproduction. It does not explicitly state when not to use the tool, but no close alternatives exist among the siblings.

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