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

Annotations already convey read-only false, destructive false, and idempotent true; the description adds the reproduction-context expectation but does not disclose side effects, response behavior, or failure characteristics. It provides some value beyond annotations but leaves the mutation behavior largely unspecified.

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, front-loaded with the main purpose, and no filler. The second sentence adds a concrete necessary instruction about the conversation array.

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 three-string-parameter tool with annotations and no output schema, the description conveys the main use and one key parameter. However, required parameter 'message' and optional 'context' remain undefined, so the tool is not fully self-contained for an agent.

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 only explains the 'conversation' parameter's purpose ('recent messages for reproduction') and leaves 'message' and 'context' inferred from context. The required 'message' field is unclear without guessing.

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 a bug, missing feature, or sending feedback. It uses a specific verb and resource, and while it doesn't explicitly differentiate from sibling tools, no siblings overlap with this function.

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 provides explicit use cases ('bug, missing feature, or send feedback') and instructs the caller to include recent conversation messages for reproduction. It lacks when-not-to-use guidance or alternative tool references, but the context is otherwise clear.

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