herdr_batch_handoff

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

With no annotations, the description must carry behavioral disclosure, and it does convey several traits: it batches up to eight independent tasks, requires active leased agents, and returns exact receipt-bound results rather than inline output. It omits failure semantics, partial-success behavior, and effects of mode/timeout, so it is adequate but not complete.

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?

The single sentence is compact, front-loaded with the action, and contains no fluff. It earns its place, though it is short given the tool's complexity.

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 7-parameter tool with no annotations and no output schema, this one-liner is not enough. It omits controller lease/fencing requirements, mode semantics, timeouts, read_lines, and result routing, leaving an agent to guess at essential invocation context.

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 description adds almost no per-parameter meaning. 'Up to eight tasks' hints at requests, but the critical controller_id, controller_lease_id, controller_fence_token, mode, read_lines, and timeout_ms parameters are left entirely 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?

The description names a clear action (deliver and collect) with a specific resource (up to eight independent tasks to active leased agents) and a concrete result (exact receipt-bound results). It is distinctive enough against siblings like herdr_handoff, though it doesn't explicitly name the alternative or scope boundary.

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: this is for batch-delivering independent tasks to already leased/active agents and retrieving receipt-bound results. However, there is no explicit when-to-use vs. herdr_handoff, herdr_collect_handoffs, or the wait tools, and no exclusions or prerequisites beyond 'active leased agents.'

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