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

With no annotations, the description fully carries the behavioral burden. It discloses concurrency, per-item status/body, input-order preservation, separate billing per item, unsupported endpoint inside a batch, potential latency for large batches, and a docs link. This is comprehensive and gives the agent confidence in side effects and cost behavior.

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?

Four sentences deliver all essential information: definition, example, concurrency and order, billing, exclusion, latency, and docs reference. No fluff, every sentence earns its place, and key facts are front-loaded. The structure is logical and scannable.

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 tool has no output schema and no annotations, the description covers the critical context: what the tool does, how many items, mixing, concurrency, per-item result format, billing, limitation, potential long duration, and a link to full docs. This is complete enough for an agent to select and invoke 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?

The schema already provides 100% coverage of the only parameter, describing items, endpoint, params, and tag. The description adds an example and reiterates the mix of endpoints but doesn't provide new parameter-level semantics beyond the schema. Per the rubric, baseline 3 is appropriate when schema coverage is high.

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 uses a specific verb phrase 'Execute up to 100 API Direct requests in a single call' and clearly identifies the resource as a batch aggregation of other endpoints. It distinguishes from siblings by explaining it can mix any of the other tools' endpoints, with a concrete example (50 twitter_user_profile + 50 instagram_user_profile). This leaves no ambiguity about what the tool does.

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?

It clearly states the primary use case (batching multiple API requests) and the limitations (no /v1/web/ai-mode, large batches can take minutes). However, it doesn't explicitly contrast with using individual endpoint tools directly, though the example and wording strongly imply the alternative. A direct statement like 'For single requests, use the specific endpoint tool' would earn a 5.

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