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

The description does not disclose side effects (e.g., whether it creates an issue, sends a notification, or modifies data). Annotations indicate it is not read-only, but the behavior beyond the description is unclear. This lack of transparency is a gap.

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 extremely concise, using one clear sentence to convey the purpose and a critical usage instruction. No unnecessary words or fluff.

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 description covers the primary purpose and a key detail for reproduction (conversation array), but it omits explanations of the other parameters, potential side effects, and any output expectations. Since there is no output schema, the description is adequate for basic usage but leaves several aspects unspecified.

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 only mentions the 'conversation' parameter, instructing to include it, but does not explain its structure or the purpose of 'message' and 'context'. With zero schema description coverage, the description adds very little to clarify parameter meaning, leaving most parameters undocumented.

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 and resource that distinguishes it from sibling tools like 'show_version' or 'connect'.

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 tells when to use it (when reporting a bug or feedback) and includes a specific instruction to include the conversation array for reproduction. However, it does not explicitly mention alternatives or situations where it should not be used, so the guidance is solid but not as explicit as the 'search_calls' example.

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