delimit_next_task

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

Discloses side effects as 'read-only on the ledger' and mentions possible return actions (BUILD, CONSENSUS, STOP) including safeguard tripping. With no annotations, this provides good behavioral context, though could detail more about caching or concurrency.

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?

Well-structured with headings (When to use, When NOT to use, Sibling contrast, Side effects), front-loaded with the main purpose, and concise without superfluous information.

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?

Covers usage context for a loop fetch, mentions return actions (covered by output schema), and with 0 required parameters, the description is comprehensive enough for an agent to invoke correctly.

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 100% and descriptions are adequate. The description doesn't add extra parameter-specific details beyond the schema, so it meets the baseline but doesn't exceed.

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?

Clearly states 'Get the next task to work on with safeguard checks' and contrasts with siblings delimit_task_complete (mark done) and delimit_ledger_list (list all), making the purpose specific and distinguishable.

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?

Explicitly provides when to use ('inside a loop session') and when NOT to use ('to mark a task done' or 'list all tasks'), along with sibling contrasts, giving clear usage boundaries.

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