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

Goes well beyond the annotations by disclosing the all-or-nothing admission model ('if any item is refused, the whole batch is refused with the billing code') and per-item billing behavior ('Each job then counts only if it succeeds'). These are material side effects not derivable from readOnlyHint/idempotentHint alone.

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?

Front-loads the core action in the first sentence and keeps to four dense, information-bearing sentences with no filler. Slightly crowded, but every sentence contributes distinct semantics.

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 by explaining the async polling flow (render.batch.get) and the admission/billing outcome. It omits auth requirements and the delivery behavior details, but is otherwise complete for a write tool of this complexity.

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 60% and the description's param-level additions ('shared default and optional delivery', up to 100 items) largely restate what the schema already encodes. It clarifies the item kind and the default-nesting behavior only marginally, so baseline 3 is appropriate against a partially 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?

States a specific verb and resource ('Submit up to 100 screenshot or PDF jobs together') and scopes it precisely, distinguishing it from the single-job siblings by noting each item is 'one render.screenshot or render.pdf each'. An agent can tell this apart from render.screenshot.create and render.pdf.create without opening a schema.

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 clear operational context: use this to submit multiple jobs at once, and 'Poll render.batch.get for progress and each job's result' names the follow-up tool explicitly. It lacks an explicit when-not-to-use (e.g. prefer the single create for one job), but the batch-vs-single distinction is strongly implied.

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