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

Annotations provide some transparency (readOnly=false, destructiveHint=false, idempotentHint=true), but the description itself does not add any behavioral details beyond the instruction to include a conversation array. It does not disclose potential side effects or outcomes, though it does not contradict the annotations either.

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, concise sentence with no redundant information. It is well-structured and easy to read.

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?

The description lacks sufficient detail for a complete understanding. It does not explain the purpose of 'context' or 'message', nor does it describe expected outcomes or error handling. The mismatch between 'array' and 'string' for conversation further reduces 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?

The description only explains the 'conversation' parameter (calling it an array of messages), but the schema defines it as a string, causing potential confusion. The 'message' and 'context' parameters are not described, leaving their meaning unclear. Coverage is low (only 1 out of 3 parameters referenced).

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 identifies the action and resource, and distinguishes it from sibling tools which serve 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?

The description does not explicitly state when to use this tool versus alternatives. It only mentions what it does, leaving the user to infer the appropriate context without guidance on when not to use it or what other tools might be more suitable.

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