spawn_docs

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

No annotations are provided, so the description carries the full burden. It discloses the optional save side effect ('Optionally save under .spawn/') but is vague about the default behavior (schema default save=true), what 'cheaper' means, and what the tool returns when save=false. This is acceptable but lacks depth.

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, front-loaded with the core purpose, and every phrase earns its place. The alternative tool mention is concise and packed with useful guidance without any fluff.

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?

For a simple read/fetch tool with 2 optional params, 100% schema coverage, no output schema, the description is mostly complete. It states what is fetched, the save option, and the cheaper alternative. The only notable gap is the absence of return-value description, but 'Fetch' strongly implies the content is returned, so it does not feel under-specified.

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%, so parameters are already well-documented. The description reinforces that the content includes guide/API/skills but adds no new details beyond schema. Baseline 3 is appropriate because the structured schema does the heavy lifting.

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 ('Fetch') and names three concrete resources: engine guide, tome API reference, and skills index. It clearly distinguishes this tool from the sibling spawn_skills by explicitly naming the alternative for skill-only needs.

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 final sentence provides explicit guidance on when to use a different tool: 'For just the skill menu with descriptions, spawn_skills is cheaper.' This gives the agent a clear selection criterion and names the alternative, exceeding a mere context implication.

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