ps_batch

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

No annotations, so the description carries the burden. It usefully discloses sequential execution, stop-at-first-error with default true, and one-result-per-op return shape. But it omits what happens when stopOnError is false (continue? collect errors?), whether partial results are rolled back, and what valid operations exist.

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 the core purpose and progressively adding the op shape and error behavior. Little waste, though the sentence fragments are terse at the cost of clarity.

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?

A batch executor with an unconstrained 'operation' string, no annotations, and no output schema. The description should enumerate supported operations or point to a discovery tool, and explain stopOnError=false behavior; neither is present.

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 compensate: it explains the {operation, args} item shape and the stopOnError default. However it never enumerates valid operation values or the args contract, leaving the most important parameter semantics undefined.

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?

States a specific verb and resource: 'Run several operations in order' with the ops structure. Clear what the tool does, but it does not differentiate itself from siblings like ps_do or ps_recipe, which also run operations, so an agent can't tell when to pick this one.

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?

No guidance on when to use this versus ps_do, ps_recipe, or ps_execute_script. The 'operation' string values that are legal are not named, so the agent has no routing signal.

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