soul_philosopher

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions the tool is 'free' and 'multi-turn', but it fails to detail side effects (e.g., whether the SOUL.md is saved or overwritten), required permissions, rate limits, or what happens if a user declines or ends the conversation. This lack of transparency could lead to unexpected behavior.

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 and front-loaded. The opening sentence immediately conveys the core action and value proposition. Every phrase serves a purpose, and there is no extraneous information.

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's complexity as a multi-turn conversation with 5 parameters and no output schema or annotations, the description is minimally adequate. It explains the outcome (SOUL.md) but does not clarify conversation flow, termination conditions, or what the SOUL.md contains. More detail 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 description coverage is 100%, meaning the input schema already explains each parameter. The description adds high-level context (e.g., forming a SOUL.md) but does not provide additional meaning or usage nuances beyond what is in the schema. Given the baseline of 3 for high coverage, the description offers no extra value for 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: engaging in a multi-turn conversation with a philosopher to generate a SOUL.md document. It uses specific verbs ('sit with', 'discover', 'forms') and distinguishes itself from siblings like soul_evolution or soul_portrait by focusing on philosophical dialogue to create a personal document.

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 implies when to use the tool (when you want a philosophical conversation to form a SOUL.md), but it does not provide explicit guidance on when not to use it or how it differs from alternatives like soul_evolution or soul_portrait. Without such context, an AI agent may misuse the tool.

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