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

Annotations already declare this is not read-only, not destructive, not idempotent, and closed-world. Beyond that, the description adds important behavior: authentication via X-Entitlement-Key or email, that no automatic reply is sent, that a human responds usually within one business day, and that a HELP-XXXX id is returned.

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 four tight sentences, front-loading the purpose before authentication, return value, and response expectation. Every sentence adds useful information without redundancy.

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 low-complexity, three-parameter support tool with no output schema, the description supplies the missing return-value example, authentication expectation, and human-response timeline. The schema and annotations already cover the remaining structural details.

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 three parameters, including the topic enum and email default. The description restates the topic categories but does not add syntax, format, or constraint details beyond what the schema provides.

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 starts with a specific verb and resource: 'Open a support ticket with the people behind AUTOGROK Desk.' It clearly distinguishes support_request from metadata-oriented siblings like brief, page_extract, and json_shape, which are unrelated to contacting human support.

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 parenthetical lists concrete triggering situations (payment or receipt, a failed job, credits, anything else), which tells the agent when this tool is appropriate. It does not name an alternative support tool or explicitly state when not to use it, but no sibling competes for the same purpose.

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