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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world). The description adds genuine behavioral context beyond that: the data is derived from DSO validator licenses on the public Scan API, and it discloses a registry quirk (only about half the fleet records a distinct sponsor; the rest name themselves, and the tool reports that rather than echoing the node name). It does not discuss pagination or result ordering.

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?

Front-loaded with the verb and resource, then return fields, then routing to siblings. Dense and largely waste-free, though the "CCPEDIA-unique... public Scan API" provenance clause and the parenthetical about self-naming sponsors are slightly verbose for a description of this 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?

With no output schema, the description compensates by enumerating the returned fields and the registry caveat, which is exactly what an agent needs to interpret results. Missing only minor operational detail such as how the fuzzy name match is ranked or how limit truncation behaves.

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%, so both parameters are already documented, including that name may be whole or partial and limit defaults to 10 with a max of 50. The description only restates "by name or party id" for the lookup key, adding no syntax or matching detail beyond the schema. Baseline 3 applies when the schema does the heavy lifting.

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?

States a specific verb (look up) and resource (an individual Canton validator node in the DSO registry) and enumerates what it returns: sponsor, Splice version and staleness, last active, earning round range, and missed reward coupons. It is clearly distinguishable from fleet-level and governance siblings.

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?

Gives explicit triggering questions ("is node X still live", "how reliable is X", "who onboarded X") and names three alternatives with the condition each covers: get_validator_fleet for fleet-wide version distribution, get_upgrade_status for MainNet minimums, list_votes_by_sv for SV governance (a different population). Nothing is left to inference.

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