ops_batch

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

With no annotations, the description carries the burden and discloses real behavioral traits: an allowlist restriction, batch-size bounds, a single filesystem pass for grep_many, and idempotency requirements for mutations. It stops short of describing partial-failure semantics or what happens to already-applied steps when a later step fails.

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?

Three dense sentences with the capability and its bounds stated first, then the search/preview detail, then the retry constraint. No filler or repetition.

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?

An output schema exists and ops_result is named for snippets, so return values are reasonably covered. The gap is on the input side: for a 1-512 step batch tool, nothing explains what a step looks like, which is what an agent most needs before calling it.

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 critical 'steps' parameter is an untyped array of free-form objects, so an agent cannot learn the step structure from either the schema or the description. Only 'idempotency_key' gets meaning ('stable ... on retries' for mutating batches); the primary parameter remains opaque.

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 concrete verb and resource ('Execute ... allowlisted file operations') and quantifies scope (1-512, one call). It also differentiates from the sibling by noting that snippets are retrieved via ops_result rather than here. The remaining ambiguity is the shape of an individual step, which is left entirely unexplained.

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 gives one conditional rule (mutating batches require a stable idempotency_key on retries) and routes snippet retrieval to ops_result, which is useful. However, there is no guidance on when to choose a batch call over individual operations, or what a failure in the batch implies.

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