offload_task

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

Annotations are absent, so the description bears full responsibility. It discloses that an external worker is used and mentions default models and latency, but it doesn't clarify whether the call is synchronous, what happens on failure, network dependencies, or cost implications. It also doesn't describe the return value or any side effects.

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 a single, efficient sentence that front-loads the core action and resource, then adds the purpose. It's not overly verbose and avoids redundancy, though it could be slightly more structured by separating the purpose from the resource list.

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?

With 5 parameters, no output schema, and no annotations, the description is too thin. It doesn't explain expected output format, error conditions, when to choose specific providers/models, or how the result is returned. An agent would need to inspect the schema or rely on defaults without clear guidance.

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 all parameters. The description adds no additional meaning beyond what the schema provides; it doesn't explain relationships between parameters or edge-case behaviors, so the baseline 3 applies.

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 uses a specific verb ('offloads') and lists concrete resources ('focused implementation subtask, utility function, unit test suite, regex, or refactoring step'), clearly distinguishing this tool from siblings like consult_architect or deliberate_council, which are about thinking rather than execution.

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?

It states the motivating purpose ('to save host agent context and execution limits') but doesn't explicitly say when to use this vs alternatives, nor when not to use it. It implies usage for small, well-defined tasks but no explicit exclusions or comparison with doing the work inline.

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