delimit_executor

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

With no annotations, the description must disclose behavior. It does so by explaining dry-run default (live=False), whitelisted actions, audit logging to a specific file, and a pause mechanism (touch ~/.delimit/pause_executor). It does not cover error handling or rate limits, but overall it provides good behavioral insight beyond the schema.

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 description is concise with 6 sentences, front-loaded with the key purpose. Every sentence adds necessary information without redundancy. It is well structured and easy to parse.

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?

Given the tool's complexity (4 params, output schema present), the description covers the essential workflow, default behavior, and logging. It does not detail error cases or output format, but the presence of an output schema mitigates missing return value details. Overall, it is sufficient for an agent to understand tool usage.

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%, so the schema already documents parameters. The description adds value by explaining the context of 'live' (dry-run default), 'executed_by' (identifier for audit log), and the actions ('run', 'poll', 'status', 'pause', 'resume'). This enriches the meaning beyond the schema descriptions.

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's purpose: 'Run approved work orders from the dashboard inbox (Pro, Worker Pool v2).' It specifies the bounded whitelist of actions and distinguishes the tool from siblings like delimit_audit or delimit_work_orders by focusing on execution of approved work orders.

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?

The description explains the workflow (dashboard Approve button, poller, one-shot call) but does not explicitly state when to use this tool versus alternatives like delimit_agent_dispatch or delimit_work_orders. Context is provided but no explicit when-not or alternative guidance.

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