Execute API operations in sequence

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so safety is covered. The description adds real behavioral value beyond that: execution halts at the first failure, which tells the agent that earlier successful steps are not rolled back and side effects may be partially applied — important for a destructive batch tool.

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?

Two sentences, both earning their place. The ordering/limit/short-circuit constraint is front-loaded, and the substitution rule plus example follow without padding.

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?

For a destructive, multi-step tool with no output schema, the description omits the return shape — whether all step results are returned, how a mid-batch failure is reported, or whether partial output is available. An agent can call it correctly but cannot anticipate the response.

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 0%, so the description must carry the load, and it does for the hardest part: the exact '$steps.<i>.<path>' syntax, dot-separated keys, and numeric array indexing, with a worked example. It does not explain the 'operation' field's provenance, but the schema already documents that as 'Operation name returned by search.'

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 states a specific verb and resource ('Run up to 20 API operations in order'), plus the batch cap and short-circuit behavior. It implicitly distinguishes itself from the single-op 'execute' sibling through 'up to 20' and sequencing, though it never names the alternatives.

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?

Usage is implied by the chaining/substitution semantics — you'd pick this over 'execute' when later steps depend on earlier results — but the description never states when to use this vs. 'execute' or 'search', nor any prerequisites. The context is inferable but not explicit.

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