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

Annotations establish readOnlyHint=true and openWorldHint=true, so safety is already covered. The description adds real behavioral detail beyond that: a hard cap of 30 epochs, newest-first ordering, dual address semantics, and a found=false sentinel for providers outside the tracked window.

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 tight sentences with no filler, front-loaded with the return shape and window before moving to address semantics and the not-found case. Every sentence carries distinct information.

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 correctly fills the gap by naming the returned fields (per-epoch reward rate, Score trend), ordering, and the found=false flag. Only minor gaps remain, such as pagination or behavior when limit is reduced below the tracked count.

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 must carry the burden, and it does for the critical required param – it explains that address may be either the entity address or the delegation address, which the bare hex pattern cannot convey. It also implies the limit behaves as 'up to 30, newest first', though it never explains what limit less than 30 does.

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 states a specific verb+resource ('Return one Flare FTSO provider's per-epoch reward-rate and Score trend') and specifies the time window. It distinguishes itself conceptually from the snapshot-style get_ftso_provider_metrics, but never names that sibling explicitly, so differentiation is inferential rather than stated.

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?

Usage is implied by the words 'trend over the last tracked reward epochs' – an agent can infer this is the historical/time-series option versus a point-in-time metrics call – but the description never states when to prefer it over compare_ftso_providers or get_ftso_provider_metrics, and lists no exclusions.

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