souldinals_load_soul

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

With no annotations, the description carries the full disclosure burden. It makes clear this is a read/fetch operation, specifies which inscription is selected, and describes the return value. It does not cover failure modes or wallet-unlock requirements, but the core behavior is transparent.

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 front-loaded with the core action and return behavior. The final tip about earning_opportunities is tangential to invocation but does not obscure the main instructions.

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?

For a single optional-parameter read tool with no output schema, the description is largely complete: it covers the operation, default address behavior, and return content. It could say more about error handling or empty results, but nothing critical for basic invocation is missing.

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 the address parameter is already fully documented. The description adds the same default-address behavior found in the schema, providing no extra semantic detail beyond that baseline.

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 states a specific verb and resource: load/display the oldest soul inscription from a Taproot address. It clearly explains the selection rule (oldest) and default address fallback, though it does not explicitly distinguish itself from siblings like souldinals_list_souls or souldinals_display_soul.

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 usage context is implied: use this to retrieve the oldest soul's content, optionally specifying a Taproot address. However, it does not state when to use this versus souldinals_list_souls or souldinals_display_soul, nor does it mention prerequisites such as wallet availability.

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