souldinals_display_soul

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

No annotations are provided, so the description carries the disclosure burden. It usefully explains that it fetches from Unisat, applies Markdown-parsing heuristics for name/description/values/focusAreas/sections, and returns raw Markdown. It does not disclose failure behavior for invalid IDs or Unisat outages, which keeps it from a 5.

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 purpose is front-loaded and the bulleted extraction rules are efficient, clarifying exactly what the return payload contains. The closing earning_opportunities tip is promotional and not relevant to invoking this tool, which is the only meaningful waste.

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?

With no output schema and no annotations, the description does a good job explaining the returned structured traits plus raw Markdown. It is nearly complete for a simple read-only parse/display tool, though it omits error and external-dependency failure behavior.

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 coverage is 100%, and the sole inscriptionId parameter already documents the required {txid}i{index} format. The description does not add format, constraints, or validation semantics beyond the schema, so the baseline 3 applies.

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 + resource: parse and display soul traits from a specific inscription. It also enumerates the exact traits extracted, making the purpose concrete. It does not explicitly contrast with sibling tools like souldinals_load_soul or souldinals_list_souls, so it stops short of a 5.

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 you need a specific inscription ID, but gives no explicit when-to-use guidance, no exclusions, and no routing relative to the souldinals_load_soul, souldinals_list_souls, or souldinals_inscribe_soul siblings. The trailing tip to call earning_opportunities is unrelated to selecting this tool.

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