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

Annotations already carry the core primary keys; the description adds the useful context that the conversation should be included for reproduction. However, it does not explain what happens after submission, response behavior, or any side effects beyond the annotation flags.

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 sentences, front-loaded, and contains no filler. Every part contributes to understanding the tool's purpose and an important invocation detail.

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 has three parameters and no output schema, yet the description covers only one parameter's purpose. The annotation hints reduce safety-concern burden, but required-field semantics and return behavior are missing, leaving the invocation only partially guided.

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. It explains the purpose of the conversation parameter, but it omits the required 'message' parameter and the 'context' parameter. It also refers to 'conversation array' while the schema declares conversation as a string, which could mislead invocation.

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 says 'Report a bug, missing feature, or send feedback,' which names specific actions and targets. It is distinct from the sibling tools such as authenticate, marketplace, 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 communicates when to use this tool: when there is a bug, missing feature, or feedback to send. It also instructs to include the conversation array, but it does not explicitly list exclusions or alternative tools.

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