ck_delegate

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

The description discloses that the tool mutates session state and transfers governance context (findings, budget, proofs). No annotations are provided, so the description carries the full burden; it adds relevant behavioral context beyond what annotations would provide.

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 well-structured and front-loaded with the core purpose. Every sentence adds value, including mode details and usage guidance. No unnecessary 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?

The tool is complex with 5 parameters and 4 modes, and no output schema is provided. The description covers the main behavior and modes but lacks details on return values, error conditions, or the shape of output for each mode.

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 80%, so the schema already documents most parameters. The description adds examples for agent values and explains modes, but does not significantly extend parameter meanings beyond the existing 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 delegates a governed task to another AI agent, transferring governance context. It lists four modes and distinguishes itself from the sibling tool ck_route by instructing to call ck_route first for recommendations and ck_delegate for handoff.

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 explicitly states when to use ck_route versus ck_delegate: 'Prefer ck_route when you only need a recommendation without transferring; prefer ck_delegate when you are ready to hand off execution.' It also instructs to call ck_route first.

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