delimit_swarm

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

With no annotations, the description carries full burden. It identifies which actions mutate state ('register', 'create_tool', etc.) and which are read-only. Discloses that each venture gets 5 agent roles with namespace isolation and model binding. Lacks details on authorization or failure modes but is fairly comprehensive.

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?

Well-structured with clear sections (When to use, When NOT to use, Sibling contrast, Side effects). Every sentence adds value, no redundant information. Front-loaded with the main 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 the tool's complexity (7 params, multiple actions, output schema exists), the description covers usage, exclusions, side effects, and high-level structure. It doesn't explain all possible actions exhaustively but provides sufficient guidance. Output schema existence is noted but not described, which is acceptable.

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 baseline is 3. The description adds context by grouping actions but does not significantly elaborate on individual parameters beyond the schema's minimal descriptions. The action parameter's default and purpose are clarified via examples, but other parameters (repo_path, target_path) remain somewhat ambiguous.

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 it manages the cross-venture agent swarm, listing specific actions like register venture, create tools, hot-reload modules. It distinguishes from sibling tools by contrasting with delimit_agent_dispatch (per-task) and delimit_agent_status/dashboard (read state).

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 'When to use' and 'When NOT to use' sections with named alternatives (delimit_agent_dispatch, delimit_agent_status/dashboard). Also provides sibling contrast, making it clear when this tool is appropriate.

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