adl_execute

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

With no annotations, the description carries the full burden: it does disclose two valuable traits — cancellation is supported and partial execution is never rolled back. However, it says nothing about permissions, what happens on revision conflict, or what handle the call returns to poll on adl_task.

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 tight sentences with the key constraint and the rollback caveat front-loaded and nothing redundant. It is arguably too terse for the underlying complexity, but there is no wasted wording.

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 mutation tool with a nested 8-action step schema, a required optimistic-concurrency parameter, no annotations, and no output schema, the description is materially incomplete — an agent cannot infer how expected_revisions must be formed or what constitutes a failed step.

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 schema is deeply nested. The description conveys only the maxItems=20 limit on 'steps' and explains nothing about the required 'expected_revisions' map or the action/session_id/expected_revision fields that determine whether a step succeeds or aborts the batch.

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: 'Start a cancellable batch of up to 20 steps.' The word 'batch' implicitly contrasts with the singular adl_act sibling, though no sibling is named explicitly.

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?

Gives a concrete follow-up workflow ('Poll adl_task') and implies batching semantics, but never says when to prefer adl_execute over adl_act or adl_wait, nor what preconditions must hold before starting a batch.

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