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'), auto-detection of git state and model, and internal string-splitting behavior. With no annotations provided, the description fully bears the transparency burden and does so thoroughly.

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 efficiently front-loaded with purpose and usage guidelines. Every sentence adds value, though it is slightly verbose. No redundant phrases; structure is logical.

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 no annotations and presence of an output schema (context signal), the description covers behavioral aspects and usage thoroughly. It omits explicit mention of return value, but the output schema likely provides that. Still, a brief note on what the tool returns would improve completeness.

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 covers all 8 parameters with descriptions (100% coverage), so baseline is 3. The description adds value by noting that comma-separated strings are split into lists internally, which is not obvious from schema alone. A small deduction for not elaborating on 'tokens_used' or 'context_fullness' beyond schema.

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 captures session state as a 'soul' for cross-model resurrection, with a specific verb ('capture') and resource ('session state'). It distinguishes from siblings like delimit_session_handoff and delimit_memory_store by explicitly contrasting use cases.

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?

Provides explicit when-to-use ('at session end or when context gets full'), when-NOT-to-use ('general memory writes' and 'full handoff orchestration'), and names alternative tools (delimit_memory_store, delimit_session_handoff). This is exemplary guidance.

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