page.batch_analyze

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

Annotations (readOnlyHint=false, openWorldHint=true) are consistent with a mutation tool. The description adds valuable behavioral details: async submission, SSRF validation, graceful degradation, rate limiting (10 RPM), and progress tracking. No contradictions.

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 description is concise with bullet points and clear sections. Every sentence adds value: main purpose, key features, and a direct call to action for polling. No fluff.

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?

Given the complexity (7 params, nested objects, no output schema), the description covers all essential aspects: parallelism limits, error handling, rate limiting, and follow-up polling. The missing output schema is compensated by describing the return of a batch ID.

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 100%, so baseline is 3. The description adds extra context: concurrency default (3), timeout default (30min), features default (all enabled), and rate limit hint. This is helpful beyond the schema descriptions.

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 clearly states 'Batch analyze multiple URLs in parallel' and distinguishes it from siblings like page.analyze (single) and page.getBatchStatus (polling). The verb+resource+scope is specific and unambiguous.

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?

The description explicitly tells the agent to use page.getBatchStatus for polling, implies when to use (batch analysis), but does not explicitly state when not to use it or mention alternatives beyond the sibling. Still, context is sufficient for correct selection.

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