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

Annotations already flag a non-read-only, destructive, open-world, non-idempotent write. The description adds meaningful context beyond that: an outbound email notification to Tineo support and the user-confirmation gate on the write. It stops short of covering duplication behavior, rate limits, or what happens after submission.

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?

Two sentences, zero filler, and the action plus its precondition are front-loaded before the trigger conditions. Every clause earns its place.

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 mutation tool with full schema coverage and no output schema, the description covers purpose, gating, and trigger conditions adequately. The main omission is any indication of what the caller receives back (e.g., the created ticket reference) or what to do if creation fails.

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 100% across all 8 parameters, including inline docs for confirmed, source, failure_context, and attachments, so the schema carries the parameter burden. The description reinforces the confirmed precondition but adds no parameter semantics (formats, id relationships, attachment limits) beyond the schema.

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?

Specific verb+resource (create a support ticket) plus the secondary effect of emailing Tineo support. It is unmistakable against the travel-oriented siblings, none of which handle support escalation.

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?

Explicit trigger conditions are given (assistant cannot complete, tool fails, capability unsupported) and a hard precondition is stated (only after the user explicitly asks or confirms). That is as close to when/when-not guidance as this tool needs.

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