delimit_work_orders

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

Describes side effects: list/show are read-only, complete writes to the work-order store. No annotations exist, so description carries full burden. Could mention more about completion behavior but is adequate.

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 clear sections (purpose, when to use, when not, sibling contrast, side effects). Front-loaded with main purpose. Every sentence adds value.

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 scope, actions, side effects, and usage guidance. Output schema exists so return values are not needed. Minor inconsistency: 'close' in description vs 'complete' in schema.

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 has 100% coverage, but description adds behavioral context for action parameter (read vs write) and notes that wo_id is required for show/complete. Adds meaning beyond schema.

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 clearly states the tool manages work orders for listing, reading, or closing. It explicitly distinguishes itself from sibling tools like delimit_ledger_add and delimit_gov_new_task.

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?

Provides explicit 'When to use' and 'When NOT to use' sections, naming specific alternative tools (delimit_ledger_*, delimit_gov_new_task/run/verify).

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