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

The annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds genuine domain context the annotations lack: the score is fee-based and its behavioral effect is reduced outbound delays for trusted swappers. It still says nothing about whether the value is time-sensitive or how the score changes, which is relevant given idempotentHint=false.

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 sentence, front-loaded with the return subject and followed immediately by the definition of the metric. No filler, no redundant restatement of the tool name.

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-parameter read-only lookup with full schema description coverage and no output schema, the description is nearly sufficient: it tells the agent what is returned and what the number means. The only missing element is any hint about value volatility or freshness, which would matter for interpreting the score.

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?

There is a single parameter with 100% schema coverage ('The swapper's address (any chain)'), so the schema carries the full burden of explaining the input. The description adds no format, chain-specific, or validation detail beyond what the schema already states, making the baseline 3 appropriate.

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 names a specific resource ('an address's swapper clout') with an explicit retrieval verb, and even defines the metric as an 'accumulated fee-based score that reduces outbound delays.' That is far more than a restatement of the name. It does not reference any sibling, but no sibling in the list covers the same concept, so differentiation is not really required.

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 guidance on when to call this versus any alternative, no prerequisites, and no exclusions. The only usage signal is the implicit 'you need an address to look this up' from the schema, which is not stated in the description.

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