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

Annotations already provide idempotentHint=true and destructiveHint=false, so the safety profile is known. The description adds the reproduction context but does not disclose any unexpected side effects or return behavior. It does not contradict annotations, but adds limited behavioral context.

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: the first states the purpose, the second gives a specific usage instruction. No fluff or redundant wording. Front-loaded with the key action.

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 tool, the description covers the primary action and the key parameter (conversation). However, it does not clarify that the conversation should probably be a JSON-encoded string, nor does it mention the 'context' field. The ambiguity around the conversation format leaves a gap in completeness.

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 clarifies that 'conversation' should be an array of recent messages for reproduction and implies 'message' is the content of the report. However, it does not explain the 'context' parameter at all, and the schema type for conversation is listed as 'string' while the description calls it an array, creating ambiguity. Partial compensation, but incomplete.

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 'Report' and resource 'bug, missing feature, or send feedback', clearly distinguishing this tool from sibling tools like authenticate or connect. The purpose is immediate and 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 implies when to use the tool: for reporting bugs, missing features, or feedback. It also provides a concrete instruction to include the conversation array for reproduction. Though no explicit alternatives are named, sibling tools are unrelated, so the implied usage is clear.

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