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

Annotations already cover the safety profile (readOnly, idempotent, openWorld=false, non-destructive), and the description adds real behavioral facts beyond them: results are limited to the last 24 hours, sorted newest first, and include per-picture progress plus a plan allowance where 0 means batches are unavailable. Those are non-obvious traits an agent would otherwise only discover at runtime.

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?

One sentence, front-loaded with the resource and scope, with no wasted wording. The trailing parenthetical about allowance is slightly crammed but carries genuinely useful semantics rather than filler.

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?

An output schema exists, so return-shape explanation is optional, and the description still usefully flags progress and allowance fields plus the allowance=0 edge case. What's missing is an explanation of how the two input parameters behave (especially limit's cap of 10) in this lightly annotated-by-schema definition.

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 compensate and does not fully. It implies the 'scene' parameter through 'batches of one scene' but never explains what a scene identifier is or its format, and the 'limit' parameter (max 10) is not mentioned at all despite governing the 24-hour result set.

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 names the resource (batches), the scope (one scene, last 24 hours) and the ordering (newest first), which is enough for an agent to know exactly what it returns. It never names a sibling like get_batch (single batch) or list_job_files, so differentiation is implicit rather than stated.

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?

There is no guidance on when to call this versus get_batch, start_batch or list_job_files, and no exclusions. The 24-hour/one-scene scope hints at applicability but the agent must infer it from a description of return content, not from explicit usage instructions.

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