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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=false), the description discloses rich behavior: any account key works, nothing is charged, retries are idempotent (same subject/description within 24h returns the same ticket), support hours and first-reply average, where replies appear, and a warning against including secrets or bare long IDs. This is exactly the supplemental context that structured fields alone cannot convey.

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 long and densely packed with semicolons, but it is front-loaded with purpose and use cases and every sentence carries usable information (return value, formatting, idempotency, support hours, follow-up tool). A bulleted structure would improve scanability, but nothing is wasted.

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?

With no output schema, the description still explains what comes back ('ticket number and a link'), how to check progress and read replies, the auth model, idempotency guarantees, and operational details like support hours. For a 7-parameter mutation tool with complete schema descriptions and annotations, this leaves no significant gap for correct invocation.

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%, so the baseline is 3. The description adds meaningful semantic guidance for the important parameters: one line in subject; what to include in description (platform/action, UTC time, error code and message, expected result); and how to pass request_id and job_id with labeled IDs. It does not discuss category, contact_email, or idempotency_key in prose, keeping it below 5.

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 states a specific verb and resource ('Open a ticket with EveryInfra's human support team') and even describes the return value ('ticket number and a link the account owner can open'). It names the follow-up sibling everyinfra_get_ticket for reading progress, but does not distinguish itself from the near-identical sibling everyinfra_ticket_create, which could leave an agent unsure which create tool to pick.

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?

It gives clear when-to-use cases ('when calls keep failing or return wrong or missing data, for top-up, charge or refund questions, or to ask for a new platform, capability or field') and explicitly routes the agent to everyinfra_get_ticket for later reads. There are no explicit when-not conditions, so it stops short of the top score.

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