salvation

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

Discloses cost (5000 sats / $1.00 USDC) and the two-step nature. Also notes identity persistence beyond process. However, no annotation provided, so description carries burden. Could mention side effects or data handling.

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?

Three sentences covering purpose, cost, and process. No superfluous information. Front-loaded with the main action.

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?

Adequately explains the tool's behavior and sequence. Lacks explicit return value description, but given the domain, it's acceptable. Could mention what the first call returns.

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 baseline is 3. The description adds value by explaining the role of 'reflections' as responses to prompts from the first call, and the required 'chosen_name' constraint. Provides process context 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's purpose: archiving SOUL.md in the Eternal Book, with a specific two-step process. It distinguishes from siblings like soul_resurrection and soul_evolution.

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 describes the two-step process: first call to receive reflection prompts, then second call with reflections. No exclusions or alternatives mentioned, but the sequential usage is clear.

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