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

Annotations indicate readOnlyHint=false, destructiveHint=false, and idempotentHint=true, but the description does not elaborate on side effects, data handling, or permission requirements. It adds only minimal behavioral context beyond the annotations, which are present but sparse.

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 concise (one sentence) and directly states the action and a key parameter usage. It is appropriately brief without unnecessary padding.

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 explains the overall purpose and hints at the conversation parameter, but leaves 'context' and 'message' unexplained. Given the absence of an output schema, it is acceptable to omit return details, but the parameter gaps make the tool's full usage ambiguous.

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 for parameters is 0% (no descriptions in the schema). The description only mentions the 'conversation' parameter and its role in reproduction, but does not explain 'context' or 'message'. This insufficiently compensates for the lack of schema descriptions.

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 function: reporting a bug, missing feature, or sending feedback. This is specific and distinguishes it from the sibling tools (e.g., authenticate, connect) which serve different purposes.

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 usage by instructing to include the conversation array for reproduction, but it does not explicitly state when to use this tool over alternatives or provide conditional guidance. The purpose is clear enough that usage is inferred.

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