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

With no annotations present, the description carries the full behavioral burden. It does add useful traits by stating the output is ranked by trust score and includes DNA summaries, but it omits the scope of ranked agents, data freshness, and whether the operation is read-only.

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?

One 11-word sentence with no filler; the key discriminator, trust leaderboard, is front-loaded and every word earns its place.

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 low-complexity tool with one optional parameter and no nested objects, the description adequately conveys what is returned. However, with no output schema and no annotations, the agent universe and the meaning of DNA summaries remain unstated, leaving some room for improvement.

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% for the single optional limit parameter, including its default (10) and max (50) values. The description adds no additional parameter-level meaning, so the baseline of 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 identifies a specific resource (an agent trust leaderboard) and specifies its ordering (by trust score) and content (DNA summaries). It is clearly distinct from sibling tools like soul_profile and soul_verify, though it relies on a noun phrase rather than an explicit verb such as retrieve.

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 guidance is given on when to use this tool versus alternatives, and no sibling tools are named for comparison. The intended use case is only implied by the phrase agent trust leaderboard, so an agent must infer when this is the right choice among the many soul_* siblings.

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