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

Annotations cover the safety profile (readOnlyHint=false, destructiveHint=true, idempotentHint=false), so the description isn't obliged to restate mutability. It still adds real behavioral context: the ticket reaches the support team, the user receives a confirmation email, and cluster_id defaults to the session's cluster. It does not address whether repeated calls duplicate tickets, which would have made it a 5.

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?

Front-loaded with the action and the when-to-use routing before the drafting advice; every sentence carries information. It is a dense run-on paragraph, so it falls short of a crisp 5, but nothing is filler.

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 mutating, no-output-schema tool, the definition covers recipient, confirmation behavior, routing alternative, defaults, and content expectations — enough to call it correctly. It omits failure/permission behavior, which keeps it below a 5.

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 100%, so baseline would be 3, but the description adds genuine meaning: it specifies what a good subject looks like and enumerates the evidence the description field should contain (expected, actual, when, cluster/resource), plus the cluster_id fallback behavior. That is more than the schema conveys on its own.

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 ('Raise a support ticket with Ankra's support team on the user's behalf') and even anchors it to the equivalent CLI command ('ankra support create'). It explicitly differentiates from the closest sibling, file_ticket, so an agent can route without opening schemas.

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?

Provides explicit when-to-use triggers (user asks to contact support, report a platform problem, escalate something the platform cannot fix) and an explicit when-not ('do not use it for work the AI board should track (file_ticket)'). It also prescribes content expectations for the ticket, which is actionable guidance beyond mere routing.

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