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

Annotations include idempotentHint:true and readOnlyHint:false, but the description adds value by instructing to include the conversation array for reproduction, which is beyond the annotations. It does not contradict any annotation; it provides helpful behavioral guidance.

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 a single, clear sentence that front-loads the purpose and includes a specific instruction. There is no fluff or redundancy; 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?

Given the tool's simplicity, three parameters, and no output schema, the description is sufficiently complete. It explains the core action and the key reproduction step, and the siblings are unrelated, so no confusion exists. Some parameter details are left to the schema, but the schema lacks descriptions, so a slightly higher detail level could improve completeness—still adequate.

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 explicitly mentions the 'conversation' parameter and implies 'message' is the bug report, but does not explain the 'context' parameter. It provides some semantic meaning but not full coverage of all 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 clearly states the tool's purpose: 'Report a bug, missing feature, or send feedback.' It uses a specific verb and resource, and distinguishes it from siblings (authenticate, connect, marketplace, etc.) which are unrelated.

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 clear context for when to use the tool—when reporting bugs, missing features, or feedback—but does not explicitly mention alternatives or when not to use it. Since no sibling tool serves this purpose, the guidance is adequate without exclusions.

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