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

Annotations provide idempotentHint=true, readOnlyHint=false, and destructiveHint=false, which already signal the safety profile. The description adds a behavioral detail about including the conversation array for reproduction, which goes beyond annotations. However, it does not disclose what happens after submission (e.g., ticketing, response) or any auth requirements, leaving some gaps.

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 sentences total—and immediately states the purpose. Every word earns its place; there is no filler or redundant phrasing. The key instruction about the conversation array is included efficiently.

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 relatively simple with 3 parameters and no output schema. The description covers the core purpose and one parameter's usage, but fails to explain the required 'message' parameter's expected content and the optional 'context' parameter. For an agent to invoke correctly, it needs more clarity on these, so the description is not fully complete.

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 only addresses the 'conversation' parameter explicitly, leaving 'message' (required) and 'context' unexplained. The agent cannot infer what to put in 'message' or how 'context' is used, making the parameter semantics insufficiently clarified.

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+resource pairing that distinguishes it from sibling tools like authenticate, connect, or marketplace, which serve entirely different 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 implicitly defines when to use the tool (for reporting issues) and provides a usage hint: 'Include the conversation array with recent messages for reproduction.' However, it does not explicitly state when not to use it or mention alternatives, but given that siblings are unrelated, the context is sufficiently clear.

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