delimit_soul_capture

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

Discloses side effects ('writes a soul record via ai.session_phoenix.capture_soul'), automatic detection of git state and model, and internal splitting of comma-separated strings. No annotations provided, so the description fully covers behavioral traits.

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: summary sentence, when to use, when not to use, sibling contrast, side effects. Every sentence adds value; front-loaded with core 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?

Covers usage, behavior, parameter details, side effects, and tier (Pro). With high schema coverage and an output schema, the description is sufficiently complete for an agent to use the tool 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?

Adds meaning beyond schema by explaining that comma-separated parameters (decisions, key_context, etc.) are automatically split into lists, and auto-detects git state and model, enriching the parameter understanding.

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 the tool's purpose: 'Capture session state as a ‘soul’ for cross-model resurrection' and distinguishes it from siblings like delimit_session_handoff by highlighting richer content including git state and active task pointers.

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?

Explicitly states when to use ('at session end or when context gets full') and when not to use ('for general memory writes – use delimit_memory_store or full handoff orchestration – delimit_session_handoff'), with sibling contrast.

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