Delimit Executor

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

Despite readOnlyHint=false and destructiveHint=false, the description adds substantial behavioral context: it reveals that live run/poll actions fire whitelisted GitHub side effects, that every invocation is logged, that touching a pause file halts execution, and that unlicensed calls return an error without running. This goes well beyond the annotations.

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 densely organized with labeled sections, front-loads the core purpose, and every sentence adds operational value. It is longer than average, but the length is justified by the critical side-effect, logging, pause, and licensing details.

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 tool with 4 parameters and no required fields, the description covers invocation conditions, exclusions, side effects, audit trail, pause mechanism, and licensing prerequisite. The presence of an output schema means return values need no further explanation, so nothing essential is missing.

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 baseline is 3. The description adds value by clarifying the live/action interaction ('run'/'poll' with live=True fire side effects) and noting that wo_id is required for action='run', which enriches the otherwise already-documented parameter meanings.

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 opens with a specific verb+resource: 'Run approved work orders from the dashboard inbox.' It also differentiates from sibling tools by naming delimit_agent_dispatch and delimit_work_orders, making the executor's role unmistakable.

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?

Explicit 'When to use' and 'When NOT to use' sections define the invocation context and point to the correct alternatives. The sibling contrast further clarifies the boundary between reading/closing work orders and executing them.

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