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

Annotations already declare readOnlyHint=true and openWorldHint=true, and the description adds meaningful return-content context: fee, reward rate, uptime, vote power, delegator count, Flare-specific score, and rank/percentile details. It also clarifies the denominator for rankings ('provider_count is the denominator'), providing behavior beyond the structured 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?

The description is a single front-loaded sentence that begins with the action and resource before listing specifics. It is dense but not bloated; the parenthetical about the denominator is important and earns its place. Slightly long due to the metric enumeration, but no word is wasted.

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 metrics and clarifying rank/percentile semantics. It also provides the needed address-format constraint. It does not cover edge cases like availability of FlareWatch Score on Songbird, but the parenthetical '(Flare)' alerts the agent to that distinction.

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 'address' is a lowercase 0x EVM address and that the provider is 'on Flare or Songbird', which effectively defines the network parameter. It could have explicitly named the network values, but the schema pattern and plain-language context make the semantics clear enough.

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 ('Return'), resource ('detailed metrics for one FTSO data provider'), and scope ('on Flare or Songbird'), with an explicit list of returned metrics. The singular 'one provider' and emphasis on rank/percentile distinguish it from siblings like get_ftso_providers and compare_ftso_providers.

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 description clearly implies use for a single provider's detailed metrics, but it does not explicitly state when to prefer this tool over siblings such as get_ftso_provider_history or compare_ftso_providers. No exclusions or alternative conditions are provided, leaving the agent to infer the intended use case.

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