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

Annotations already establish readOnly, non-destructive, open-world behavior, yet the description adds real operational context beyond them: a polling rate limit, a seven-day retention window after deadline, and the guarantee that terminal jobs never auto-resume. It stops short of describing authentication requirements for the required api_key or pagination behavior for the 50-job listing.

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 purpose and mode distinction are front-loaded in the first sentence, and the remaining sentences are short, information-dense fragments with no filler. The telegraphic style ('Free, nondestructive.') is terse but readable and each line carries a distinct fact.

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 an output schema present, the description needn't explain return values, yet it spends sentences on field semantics for 'ready' and 'matched', which partially duplicates that schema. It covers retention and rate limits but omits how expired jobs or invalid job_ids behave, leaving a modest gap for a tool with a required credential parameter.

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 0%, so the description must carry the load; it partially does by implying job_id is optional and drives the single-vs-list behavior ('your latest 50 jobs'), and that 'private' implies an api_key. Neither parameter is explicitly named or explained, so an agent still lacks field-level guidance on the required api_key.

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 gives a specific verb and resource ('Read a private readiness/callback job') and immediately clarifies the two modes: a single job by id or the latest 50 jobs when no id is supplied. It does not, however, name the closely related siblings cancel_readiness_job or wait_until_ready, so the agent must infer the boundary itself.

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?

Usage is implied by the dual mode description and a concrete polling constraint ('Poll no faster than every 15 seconds'), and 'Free' signals cost expectations. There is no explicit when-to-use/when-not guidance relative to wait_until_ready or cancel_readiness_job, so an agent cannot resolve which tool to pick from the description alone.

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