rew_batch

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

Beyond the annotations (destructiveHint=true), the description discloses the critical partial-failure semantics: it halts on the first error or unfinished async action and does not roll back earlier actions. That is exactly the kind of behavior an agent needs before firing a destructive batch. It stops short of explaining how results of each step are returned or how async waiting behaves.

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 short sentences, front-loaded with purpose followed by failure semantics and the identifier rule; nothing is redundant or padded.

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 failure and non-rollback behavior is well covered for a destructive batch tool, which is the highest-risk aspect. However, with a nested step schema at 0% coverage and no output schema, the absence of any explanation of step fields or async wait mechanics leaves the agent guessing about how to construct calls 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 description coverage is 0%, and the steps array has eight nested fields (method, path, body, query, wait, wait_timeout, progress_path) with no documentation. The description only adds the 'UUIDs, not indices' hint for path identifiers; the async-control fields wait, wait_timeout, and progress_path, which materially change execution, are left unexplained.

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?

A specific verb and resource — 'Execute an ordered API workflow' — tells the agent this runs a sequence of API calls as a batch. The name rew_batch and siblings like rew_call_api and rew_request suggest the distinction, but the description never explicitly contrasts itself with a single-call tool.

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?

There is no explicit when-to-use guidance and no alternative tools are named or excluded; an agent must infer that this is the multi-call path versus the single-call siblings. 'Use UUIDs, not indices' is a data-format constraint, not usage guidance.

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