sc_spawn

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

With no annotations, the description must disclose behavioral traits, but it only says 'create specialized agents' with no detail on side effects, permissions, reversibility, or operational behavior. The mutation implied by 'create' is stated, but nothing else is disclosed.

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 short but redundant: 'Create specialized agents' and 'Spawn task-specific AI agents' say essentially the same thing. It is not verbose, but a single concise sentence would be more effective without redundancy.

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 4 parameters including a nested evidence object, no output schema, and no annotations, the description is minimal. It fails to explain how the flags/persona relate to spawning or what the expected outcome/return is. A more descriptive overview is needed for effective invocation.

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 100%: args, flags, persona, and evidence all have descriptions and enums. The description adds no parameter-level meaning, but the schema already provides sufficient semantics, meeting the baseline for full coverage.

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 states the tool creates/spawns task-specific AI agents, which is a clear verb-resource pair. It distinguishes from sibling tools that perform actions like build, test, or analyze, though it doesn't explicitly contrast with them. The wording is slightly redundant but the purpose is evident.

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 usage context is provided. The description does not say when to use this tool versus alternatives, nor does it mention any prerequisites or exclusions. An agent is left without guidance on selecting sc_spawn over other sc_* commands.

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