compare_validators

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

No annotations are provided, so the description carries the full behavioral burden and largely fails to: it never states this is a read-only operation, what fields or metrics are returned, or whether results are ranked. 'By performance and metrics' is the only hint about output shape.

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?

A single tight sentence with the action front-loaded and no filler. It is efficient but extremely sparse, so it stops short of earning a 5.

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 tool with no annotations, no output schema, and 0% parameter documentation, the description should disclose the return shape and how limit/sortBy affect results. It omits all of this, leaving an agent to guess what comparison output looks like.

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 0% and the description never mentions the limit or sortBy parameters. The sortBy enum values (apy, uptime, reputation, total_staked) are self-explanatory, but the description adds no meaning beyond them and leaves limit semantics (max validators returned?) undefined.

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 (compare) and resource (Chiliz validators) plus the axes (performance/metrics), which is enough to distinguish it from read-only siblings like get_validator_performance. However, it does not explicitly name which sibling answers a different question, so sibling differentiation is only implied.

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?

There is no when-to-use guidance, no condition for choosing this over get_validator_performance or get_validator_risks, and no prerequisites. The comparison framing only weakly implies usage.

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