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

Annotations provide idempotentHint=true and destructiveHint=false, so the description doesn't need to repeat that. The description adds that including the conversation array helps reproduction, which is a behavioral expectation beyond the schema. It does not contradict 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 provides a key usage hint. Every sentence earns its place with no redundancy.

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 (3 params, 1 required), and annotations cover idempotency and non-destructiveness. However, the description doesn't explain what happens after reporting (e.g., no response, ticket creation) or how the conversation array should be formatted. For a bug-report tool, this is likely sufficient, but some completeness is lacking.

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% (context, message, conversation have no descriptions), so the description must compensate. It explains the 'conversation' parameter by advising to include recent messages for reproduction, which adds meaning. However, it doesn't clarify 'context' or the format of 'conversation' beyond the default, leaving some ambiguity.

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.' This is a specific verb (report) with a clear resource (bug/feature/feedback). It is distinct from siblings like authenticate or marketplace, though it could further differentiate from generic feedback tools.

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 indicates when to use this tool: to report bugs or missing features or send feedback. It also instructs to include the conversation array for reproduction, which provides practical guidance. However, it doesn't explicitly state when not to use it or alternative tools for other feedback types.

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