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

Annotations already convey that the tool is not read-only, not destructive, and idempotent. The description adds a meaningful behavioral instruction: include the conversation array for reproduction. It does not detail side effects or what happens after submission, but with annotation coverage this is acceptable.

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?

A single front-loaded sentence conveys the core purpose and the key reproduction instruction without waste. Every word earns its place.

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?

For a simple three-string-parameter tool, the description covers the main purpose and one important usage detail, but it omits parameter-level guidance for message and context. There is also no output schema, and the return behavior is not addressed, leaving a moderate completeness gap.

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 explain the parameters. It only mentions the conversation array; the required message parameter is implied but never explicitly described, and the context parameter is entirely unaddressed. This leaves the agent guessing about two of three parameters.

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 states a specific verb and resource: "Report a bug, missing feature, or send feedback." This clearly distinguishes report_bug from the many calculo_* calculator siblings and other utility tools.

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 gives explicit usage contexts: bug reports, missing features, and general feedback. It does not name alternatives or exclusions, but no sibling tool appears to compete for this purpose, so the context is clear enough.

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