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

Annotations already indicate it's not read-only, not destructive, and idempotent. The description adds context about including conversation data for reproduction but does not disclose what happens after submission (e.g., where the report goes, any side effects). It adds some value beyond annotations but lacks behavioral specifics like confirmation or storage.

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 concise sentences, front-loaded with the tool's purpose and immediate usage instruction. No wasted words.

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 feedback tool with no output schema and minimal annotations, the description covers what it does and how to use it. It lacks detail on post-submission behavior or parameter specifics, but given the low complexity, it is reasonably complete.

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 coverage is 0%, so the description must compensate. It clarifies the purpose of the 'conversation' parameter (recent messages for reproduction) but leaves 'context' and 'message' vague. The description's mention of 'conversation array' conflicts slightly with the schema's string type, but that is a schema issue. Marginal value added.

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?

Description clearly states the tool's purpose: report a bug, missing feature, or send feedback. The verb 'report' and noun 'bug/feature/feedback' are specific and distinct from sibling tools like authenticate or show_version, which have different functions.

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?

Description gives usage context by instructing to include the conversation array for reproduction, which implies when to use (when reporting issues). It does not explicitly mention alternatives or when-not to use, but no sibling tools overlap in functionality, so the guidance is sufficient.

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