delegate_task

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

With no annotations, the description carries the full burden. It discloses a key behavioral trait: the parent's status changes to 'delegated'. It also mentions delegation chain recording. However, it omits details like authorization requirements, reversibility, or behavior when the parent is already delegated.

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 two sentences with zero wasted words. It front-loads the primary action and then provides usage guidance, achieving maximum efficiency.

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 has 8 parameters and no output schema, the description covers core function and sibling differentiation but lacks return value information, error handling, or prerequisites. It is adequate but not fully complete for the complexity.

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% with descriptions for all 8 parameters. The tool's description adds no additional meaning beyond what the schema already provides. The baseline of 3 is appropriate since the description does not compensate for any gaps.

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?

Description clearly states the tool creates a child task linked to a parent and flips parent status to 'delegated'. It uses a specific verb-resource combination and explicitly distinguishes from the sibling assign_task by noting multi-agent handoffs and delegation chain recording.

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 advises using this tool over assign_task for multi-agent handoffs to record the delegation chain. However, it does not provide when-not-to-use guidance or address exclusions like prerequisites or edge cases.

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