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

Annotations already convey safety profile (not read-only, idempotent, not destructive). The description adds the useful context that conversation data is needed for reproduction, but it does not disclose response behavior, persistence, or any other side effects beyond the obvious reporting action.

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?

Two sentences front-load the purpose and provide the key usage note without filler. Every sentence contributes functional guidance.

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 no-output-schema feedback tool, the description covers purpose and a key input requirement. It is adequate but leaves gaps around the context parameter, expected response, and exact conversation formatting.

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 (include recent messages) but leaves context unexplained and only implies that message holds the report text; the serialized string format for conversation is also not clarified.

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 identifies the tool as a reporting channel: 'Report a bug, missing feature, or send feedback.' It uses a specific verb and resource and is distinct from sibling tools like 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 enumerates the intended use cases (bug, missing feature, feedback) and instructs the user to include the conversation array for reproduction. It does not explicitly state exclusions or alternatives, but none of the sibling tools overlap with bug reporting.

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