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

Annotations already declare non-idempotent, open-world, non-read-only behavior; the description adds the consequential detail that each call creates a NEW request and must not be auto-retried on an uncertain result — exactly the information an agent needs when idempotentHint=false.

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?

Four tight sentences, front-loaded with the action, then constraints, then retry behavior. No filler and every clause carries a distinct fact.

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?

An output schema exists so return values need not be restated, yet the description still notes a confirmed ticket ID is returned. Combined with the mutation, retry and scope caveats, an agent has everything needed to invoke this correctly.

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 coverage is 0%, so the description must carry parameter meaning. It adds content guidance for the description field (problem, proposed behavior, use case) but says nothing about the title field or the length limits, leaving one of two parameters undocumented.

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?

States a specific verb and resource ('Submit a feature request to Synoptic support') plus scope ('on behalf of the signed-in user'). It also explicitly negatives what the tool is not ('does not implement a feature'), which cleanly separates it from the create_*/update_* siblings.

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?

Gives clear when-to-use content guidance (describe the problem, proposed behavior, use case) and a strong when-not statement ('does not implement a feature or guarantee delivery'), plus an operational exclusion ('do not automatically retry an uncertain result'). It doesn't name a sibling alternative, but the other request_* tools serve unrelated resources rather than being substitutes.

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