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

Annotations already provide safety hints (readOnlyHint=false, destructiveHint=false, idempotentHint=true), and the description does not contradict them. The description adds context that the conversation array is used for reproduction, which is a useful behavioral detail. However, it does not disclose side effects, confirmation behavior, or any rate limits, so it adds only modest value beyond annotations.

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 two sentences long, front-loaded with the purpose, and contains zero unnecessary words. The second sentence provides a targeted, actionable tip about the conversation array. This is appropriately sized for a simple tool.

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 tool with no output schema, the description plus annotations and schema are fairly complete. It states the purpose, indicates the key parameter to include, and the schema provides required and optional fields. It lacks explicit guidance on the 'context' parameter, but the tool is simple enough that the missing detail is unlikely to cause major misuse.

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 by explaining parameters. It only explains the 'conversation' parameter (needed for reproduction), while 'message' and 'context' receive no explicit explanation. 'message' can be inferred from the tool's purpose, but 'context' is completely vague, leaving the agent without enough meaning to reliably populate all parameters.

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 uses a clear verb ('Report') with specific resources ('a bug, missing feature, or send feedback'), making the tool's purpose immediately obvious. It clearly distinguishes from sibling tools like authenticate, marketplace, and show_version, which serve unrelated 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 implies the tool should be used when a user wants to report a bug or provide feedback, but it does not explicitly state when to use it vs. alternatives or when not to use it. The instruction to 'Include the conversation array' is a how-to detail, not a usage guideline. No exclusion or alternative guidance is provided.

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