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

Even with readOnlyHint=true, the description adds valuable behavioral details beyond annotations: rows are returned in the supplied order with no re-ranking, Flare and Songbird rows expose different fields, and missing addresses return found=false with null fields. No contradiction with annotations.

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?

Three tightly packed sentences: purpose and scope, ordering guarantee, and per-network/missing-address behavior. Every sentence adds information, and the main action is front-loaded.

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 read-only comparison tool with no output schema, the description covers what is needed: the selection criteria, the provider limit, the per-network returned fields, row ordering behavior, and the error representation for missing addresses. No critical calling context is missing.

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%, so the description carries the burden. It explains that 'network' selects Flare or Songbird and that 'addresses' are provider addresses with a 10-item limit. It also adds missing-address behavior. The address pattern and requiredness are left to the schema, which is acceptable.

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 opens with a specific verb and resource: 'Side-by-side comparison of up to 10 FTSO providers on Flare or Songbird.' It clearly distinguishes this from sibling list tools like get_ftso_providers by emphasizing comparison and the 10-provider limit.

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 intended use case is implied clearly: comparing specific FTSO providers side-by-side. However, it does not explicitly state when not to use it or name alternatives such as get_ftso_providers or get_ftso_provider_metrics, leaving the routing decision partially to inference.

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