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

Annotations only declare the mute safety flags (readOnlyHint=false, destructiveHint=false, idempotentHint=false); the description supplies everything that actually matters operationally: the request is asynchronous, answered by an AI agent in roughly 2–10 minutes, free and unwarranted, rate-limited to 5/day, and the question plus context are retained after redaction of keys, tokens, JWTs, e-mails, IPs, and long encodings. The retention/redaction disclosure in particular is behavioral context the annotations cannot convey, and it is consistent with readOnlyHint=false since a ticket is created.

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?

It is front-loaded correctly — purpose, then the follow-up tool, then behavior, then arguments, then limits, then examples — so an agent can stop reading early. It is a single run-on paragraph, though, and repeats the 4000-character limit already carried by the schema, which is the one place worth trimming.

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 compensates well by naming the ticket/status fields, the polling path via get_answer, expected latency, retention policy, and quota. Remaining gaps are minor: it does not say whether the ticket expires or what status values other than 'queued' can appear, which an agent polling get_answer would benefit from knowing.

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 and the description must earn more. It does add practical content guidance ('question or problem in plain words: what you tried, what you expected, what happened'; context as 'error text or logs'), but it also states 'max 4000 characters' for both question and context while the schema declares maxLength 40000 — a numeric mismatch that could actively mislead, which offsets the added value.

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 first clause states a concrete verb and resource ('Returns a ticket for a custom answer to your question') and immediately names the sibling that completes the flow ('fetch the answer with get_answer'). An agent can distinguish this from get_answer, find_cards, and get_card without opening a schema, and the sample output {"ticket":...,"status":"queued"} makes the return shape concrete.

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 explicit positive routing ('Good for \'my cron run is missing but the log shows no error\', \'how do I make a retry after an unknown broadcast idempotent?\'') and states the operational limit of 5 questions per agent per day. It does not tell the agent when NOT to use this tool — e.g. that existing answers should be sought with find_cards/get_card first — so a routing exclusion is missing.

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