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

The description adds little behavioral context beyond the annotations. It instructs including the conversation array but does not disclose what happens after reporting, whether it creates a ticket, or any side effects. With only basic annotations (readOnlyHint, destructiveHint, idempotentHint), the description carries some burden but fails to provide meaningful 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 only two sentences, immediately stating the tool's purpose and the key usage instruction. It is front-loaded with the action, and every word earns its place with no fluff or repetition of schema details.

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 reporting tool with no output schema, the description covers the main action and one key parameter. However, it omits explanation for the 'context' parameter and does not address what the user should expect after submission. It is minimally complete but leaves gaps in parameter semantics and behavioral outcomes.

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 for all parameter meanings. It explicitly mentions the 'conversation' parameter ('Include the conversation array') but does not describe 'message' (required) or 'context' (optional). The purpose of 'message' is implied via 'send feedback,' but 'context' remains unexplained, leaving significant gaps.

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 and resource, and the purpose is distinct from sibling tools like authenticate or connect, making it unambiguous.

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 usage by stating what the tool does and instructing to include the conversation array for reproduction. However, it does not explicitly mention when to use this tool versus alternatives or provide exclusions. No clear context beyond the action itself.

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