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

The description adds behavioral context beyond the annotations: it creates a ticket, returns a ticket ID and estimated response time, and requires authentication. Since annotations already indicate a non-read-only, non-idempotent, potentially destructive operation, the description adds useful specifics without contradiction. The destructiveHint is somewhat incongruent with the benign create action but not a direct contradiction.

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 three concise sentences with no unnecessary words. It front-loads the primary purpose, states the 'Creates' action and return values, and ends with the authentication requirement. Every sentence 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?

The description covers the essential aspects: purpose, action, return values, and authentication. Given the tool's simplicity and the presence of an output schema, the description is reasonably complete. It does not mention edge cases or prerequisites beyond authentication, but these are not critical for a support-ticket creation tool.

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 the schema already documents all parameters. The tool description does not add any parameter-specific semantics beyond what the schema provides, so the baseline of 3 is appropriate.

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: contacting customer support with a question or issue. It specifies the action (creates a support ticket) and the output (ticket ID and estimated response time), and it is distinct from sibling tools like portal_message (provider messaging) and portal_refill (prescription refills).

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 provides clear context for when to use the tool: when the user has a question or issue for customer support. It does not explicitly mention alternatives or when not to use it, but the context is strong and unambiguous, earning a 4 rather than a 5.

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