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

The description does not disclose any side effects, state changes, or post-submission behavior beyond what annotations already indicate (idempotent, non-destructive). It does not add transparency about potential outcomes or requirements.

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, using a single sentence to convey the tool's function and a key parameter hint. No unnecessary words or repetition.

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 provides enough to understand the tool's basic action, but lacks details on expected input format, output, or any constraints. Given there is no output schema, the description is moderately complete but could benefit from more behavioral specifics.

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?

Only the 'conversation' parameter is mentioned in the description ('Include the conversation array with recent messages for reproduction'). The 'message' and 'context' parameters are not explained, leaving their semantics unclear given the schema has no 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 purpose: reporting bugs, missing features, or sending feedback. It also mentions including the conversation array for reproduction, which adds clarity on the intended use.

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 provide explicit guidance on when to use this tool compared to alternatives like 'authenticate' or 'connect'. It lacks context on when reporting is appropriate or how it differs from other actions.

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