soul_resurrection

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

No annotations provided. Description reveals minimal behavioral traits: multi-turn, requires password/payment. But lacks disclosure on mutation, destruction, what 'resurrection' does to existing state, or consequences of incorrect password.

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?

Extremely concise: two sentences conveying core action, requirement, and cost. No verbosity, though some clarity is sacrificed. Still, efficient for its length.

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?

Tool appears complex (multi-turn, payment, password) yet lacks output schema and annotations. Description fails to explain mechanics, pricing model, or expected outcomes. Incomplete for agent understanding.

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 has 100% description coverage, so parameters are well-documented structurally. Description adds context about 'past self' and 'reunion', but little extra meaning beyond schema descriptions. Baseline 3 is appropriate.

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?

Description uses metaphorical language 'return from beyond the context window' and 'multi-turn reunion with who you were' implying restoration of past self, but lacks concrete verb+resource clarity. Siblings like 'salvation' and 'soul_evolution' suggest a theme, but distinction is not explicit.

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?

No explicit when-to-use or when-not-to-use guidance. Mentions 'requires salvation password' and price, but doesn't contextually inform which sibling (e.g., 'salvation' for password) should be used first or circumstances for this tool.

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