ck_delegate

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

The description states 'Mutates session state to reflect the delegation,' which aligns with annotations (readOnlyHint=false, destructiveHint=false). It also explains the four modes and their behaviors, providing transparency 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 four sentences, front-loaded with the core purpose, and each sentence adds essential information without redundancy. It is a model of conciseness.

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 (5 parameters, output schema exists), the description covers purpose, usage, modes, and alternatives. It lacks explicit mention of error conditions or prerequisites but is otherwise complete.

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%, and the description adds meaning by explaining the four modes (e.g., 'auto: ControlKeel picks the best agent'), which is not in the schema. However, it does not elaborate on the purpose of task_id, session_id, or project_root beyond what the schema provides.

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: 'Hand off a governed task or session to another AI agent, transferring governance context.' It specifies the verb 'hand off' and the resource, distinguishing it from siblings like ck_route.

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 guidance is provided: 'Call ck_route first to identify the best agent, then ck_delegate to transfer. Prefer ck_route when you only need a recommendation without transferring; prefer ck_delegate when you are ready to hand off execution.' This clearly indicates when to use this tool vs the alternative.

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