alterlab_batch

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

No annotations provided, so description carries full burden. It discloses asynchronous behavior, pre-debiting of credits, refund policy, and the ability to configure per-URL options. This goes beyond the schema and is sufficient for a safe understanding.

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?

Very concise: three sentences that front-load the core purpose and key behaviors. Every sentence adds value, with no wasted words.

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 no output schema, the description covers the return value (batch_id), polling mechanism (alterlab_batch_status), and credit behavior. It does not detail the response structure but provides enough context for an agent to use the tool correctly.

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 the schema already documents parameters well. Description adds context about per-URL customization and the max of 100 URLs, but the parameter semantics are largely covered by the schema. Baseline 3 is appropriate.

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 it submits up to 100 URLs for parallel scraping and explicitly distinguishes from repeatedly calling alterlab_scrape. It specifies the resource (batch scraping) and action (submit), with a sibling reference.

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?

Provides clear usage guidance: use instead of alterlab_scrape for multiple URLs, and use alterlab_batch_status to poll results. Does not explicitly mention when not to use (e.g., single URLs), but the context is adequate.

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