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

Annotations already declare the safety profile: non-read-only, non-destructive, and idempotent. The description adds useful context by explaining that the conversation array aids reproduction, but it still does not disclose what side effects occur after reporting or whether authentication is required.

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 concise sentences with no filler. The primary purpose is front-loaded, and the reproduction guidance is placed at the end without unnecessary 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?

For a simple three-parameter tool with no output schema, the description covers the core action, the required message, and the optional conversation data. It is sufficiently complete to invoke the tool, though it could explain the context parameter and post-submission behavior.

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 conversation parameter as an array of recent messages for reproduction, but it does not clarify the meaning of the context parameter. The required message parameter is self-explanatory from the tool's purpose.

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 reports bugs, missing features, or feedback, using a specific verb and resource. It is distinct from sibling tools such as authenticate, marketplace, and show_version, making its purpose unambiguous.

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 provides clear usage context: use it to report a bug, missing feature, or send feedback. It also instructs agents to include the conversation array for reproduction, but it does not explicitly mention when not to use it or name alternatives.

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