spawn_from_profile

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

With no annotations, the description must disclose behavioral traits. It mentions variable interpolation and per-call overrides, and that the 'coder' profile injects Karpathy discipline guidelines. However, it does not fully describe side effects (e.g., job creation, notification routing) or permissions needed. This is adequate but not 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?

The description is concise with four sentences. It front-loads the main purpose, then adds relevant usage tips and profile list. No redundant information, though the list of profiles could be formatted slightly better.

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 tool with 8 parameters, no output schema, and no annotations, the description provides sufficient context: purpose, prerequisite (list_profiles), key features (interpolation, overrides), and profile examples. It omits details about return values, but the agent can infer it returns a job identifier. Overall, it is complete enough for correct 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 coverage is 100%, so baseline is 3. The description adds value by listing built-in profiles (aiding profile_name choice) and clarifying that override parameters allow per-call changes. This goes beyond the schema's basic descriptions.

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 'Spawn an agent job from a saved profile,' specifying the verb (spawn) and resource (agent job from profile). It distinguishes from siblings like 'spawn_agent' by emphasizing the use of predefined profiles. Mentioning variable interpolation and per-call overrides adds specificity.

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 description explicitly guides the agent to call 'list_profiles' first to see available profiles, lists built-in profiles, and recommends the 'coder' profile for general coding tasks. It provides clear context but does not explicitly state when not to use this tool versus alternatives like 'spawn_agent'.

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