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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuinely useful behavior beyond that: it discloses the return payload shape (counts by status, completion flag, per-job state/usage/result link), which matters because there is no output schema. It omits any note on polling cadence, pagination, or behavior for an unknown/expired batch id.

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 compact sentence, front-loaded with the resource ('A batch's progress') before the detail. No filler sentences. It is a noun-phrase fragment rather than a full sentence, and the trailing 'result link once succeeded' is slightly awkward, but nothing needs to be cut.

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 correctly takes on the burden of describing the return payload, and it does so for the main fields. Combined with annotations that fully cover the safety profile, an agent has enough to call it correctly. Missing only edge-case behavior (invalid id, terminal failure states, result link availability timing).

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?

There is a single parameter with 100% schema description coverage ('A batch id returned by render.batch.create'), so the schema already carries the semantics. The description adds nothing about batch_id format, lifetime, or invalid-id behavior, so this sits at the baseline for a fully documented schema.

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 a specific resource (a batch) and enumerates exactly what is returned: status counts, a done flag, and per-job state/usage/result link. That is more informative than the title 'Get batch'. It does not, however, explicitly distinguish itself from the nearby render.job.get or render.batch.create siblings, leaving the agent to infer the batch-vs-single-job boundary.

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 only implied: the 'whether it is done' clause hints at polling a batch after render.batch.create, but there is no explicit when-to-use, no exclusions, and no named alternative such as render.job.get for inspecting one job. The agent can guess the workflow but is given no routing guidance.

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