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

Annotations already declare readOnlyHint=true and openWorldHint=true, yet the description still adds real context: the tool is free, it is safe and intended to be polled repeatedly, failed runs explain the cause and the retry schedule, and the result is guaranteed to arrive eventually. Missing are lifecycle details such as how long a finished job's result remains retrievable and what a pending (neither done nor failed) run looks like.

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?

Reasonably short with no filler, but the prose is telegraphic and the meaning is front-loaded into a sentence fragment ('Free: a ticket's standing, and its result once the run is done'). The closing clause 'it's owed a result' is opaque and costs the reader more than it gives.

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 one-parameter read-only polling tool with a fully documented schema and no output schema, the description covers the essential workflow: how to get an id, that polling is allowed, and what success and failure look like. Only edge cases (pending state, result expiry, polling cadence) are left unspecified.

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% and the single parameter is already documented as the job id with a pattern and length bounds, so the baseline is 3. The description adds origin semantics beyond the schema: the id comes from a job object returned by a slow tool invoked with ticket=true, which tells the agent where to obtain a valid value rather than guessing.

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?

States the resource and what is returned: a job's standing plus its result once the run completes. The verb is implied rather than written, and the phrasing 'a ticket's standing' leans on jargon the agent must infer, but a reader can still tell this retrieves status for a job id. Siblings are unrelated utilities, so no differentiation is needed.

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?

Gives the entry condition ('a slow tool called with ticket=true answers with a job; pass its id here') and explicit permission to poll repeatedly ('as often as you like'). It does not say when not to call it or whether polling should back off, but the intended workflow is clear from the text.

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