bulk_render

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

No annotations are provided, so the description carries full burden. It mentions returning base64-encoded output but does not disclose potential side effects, rate limits, authentication requirements, or whether the tool is read-only or destructive. Does not mention that output_dir saves files to the filesystem.

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?

Single sentence containing all essential information: batch size limit, supported render types, and return format. No unnecessary words or redundant details.

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?

The description is minimal given the tool's complexity (nested jobs with many options). No output schema exists, and the description does not explain the return structure beyond base64 encoding (e.g., per-job status, errors). The schema covers input params adequately but the description could provide more context about the response format.

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 100% with detailed descriptions for each parameter and nested object. The description adds no new meaning beyond what is already in the schema, meeting the baseline of 3.

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?

Description clearly states it submits up to 20 screenshot or PDF render jobs in a single request and returns base64-encoded results. This distinguishes it from siblings like take_screenshot and generate_pdf which are singular operations.

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?

Implicitly suggests usage for batch operations by mentioning 'up to 20 jobs in a single request', but lacks explicit guidance on when to use this tool versus the singular alternatives. No when-not or exclusion criteria.

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