expand_host_plan

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

No annotations provided; description carries full burden. 'Expand' implies mutation but no disclosure of side effects, approval needs, or blocking behavior. Minimal behavioral context for a complex operation.

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?

Two sentences, no redundancy. First sentence states action, second states return. Front-loaded with key purpose.

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 7 parameters, no annotations, no output schema, description is too sparse. Does not explain prerequisites (e.g., run_id, swarm_id relationships), return format, or how discovered_files are processed. Inadequate for agent to use correctly.

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 0%; description adds no parameter-level details beyond hinting at discovered_files. Six other parameters (reason, run_id, swarm_id, host_run_id, descriptions, workspace_root) remain unexplained, leaving agent uninformed.

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 tool expands a host-native swarm/plan run with file-scoped subtasks and returns pending waves. Verb 'expand' and resource 'host-native swarm/plan run' are specific. Distinguishes from list/stop subtask siblings, but jargon may be unclear.

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?

No explicit guidance on when to use this tool vs alternatives like execute_subtask or report_host_wave. Implies use when discovered files exist but missing context for sibling differentiation.

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