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

Annotations indicate idempotentHint=true, readOnlyHint=false, destructiveHint=false. The description adds that it includes conversation for reproduction, which is useful context. However, it doesn't disclose what happens after reporting (e.g., whether it creates a ticket, sends an email, or logs), nor does it mention any side effects beyond the action. Since annotations already cover safety, the description adds some value but not extensive behavioral detail.

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, front-loaded with the purpose, and every sentence adds value. It is concise and well-structured, with no wasted words.

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?

Given the tool's simplicity (3 params, no output schema, no nested objects), the description is adequate but not complete. It explains the purpose and the conversation parameter, but lacks details on expected message format, context usage, or what happens after submission. For a reporting tool, it could benefit from more context on how the report is processed, but it's not severely incomplete.

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 mentions 'Include the conversation array with recent messages for reproduction,' which explains the 'conversation' parameter's purpose. However, it doesn't explain 'message' or 'context' beyond what the schema provides (message is required, context has default). The description adds some meaning for conversation but not for the other parameters, so it partially compensates.

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 specific verbs and resources, and it distinguishes from siblings by focusing on reporting issues rather than authentication, connecting, or querying certificates. However, it doesn't explicitly differentiate from potential other feedback tools, but given the sibling list, it's clear enough.

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 when to use this tool (when reporting bugs, missing features, or feedback) but does not provide explicit guidance on when not to use it or alternatives. It mentions including the conversation array for reproduction, which gives some context, but lacks exclusions or alternative tool references.

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