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

Annotations already indicate readOnlyHint=false and destructiveHint=false, so the report action is understood as a write but safe. The description adds the detail about including conversation for reproduction, which is useful behavioral context. However, it does not disclose what happens after reporting (e.g., confirmation, persistence, side effects). With annotations present, the bar is lower, but the description adds only minimal extra context.

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 extremely concise—two short sentences. The main purpose is front-loaded in the first sentence, and the second sentence adds a critical usage detail. There is no fluff or redundant information, making it efficient and well-structured.

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 tool is simple with only 3 parameters and no output schema. The description covers the main purpose and one parameter usage hint. However, it omits what happens after the report (e.g., success/failure indication) and doesn't explain the 'context' parameter. For such a straightforward tool, it is adequate but not fully comprehensive.

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 explicitly explains the 'conversation' parameter's purpose ('with recent messages for reproduction'), which adds value. However, it does not describe the 'message' (required) or 'context' parameters, leaving their semantics to inference from the tool's purpose. The partial compensation earns a 3.

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 uses a specific verb ('Report') and identifies the resource (bug/feature/feedback). It is distinct from all sibling tools, which are unrelated (authenticate, connect, marketplace, etc.).

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 gives a usage hint ('Include the conversation array with recent messages for reproduction') but does not explicitly state when to use the tool relative to alternatives or any exclusions. There are no obvious sibling alternatives, so it is acceptable but could be more explicit about use cases or when not to use.

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