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

The description adds behavioral context beyond the readOnlyHint and openWorldHint annotations by disclosing the data source ('FlareSystemsManager on-chain reads') and the failure mode ('Nulls returned when on-chain read fails'). This is valuable, though it does not mention caching, latency, or whether reads are live versus batched.

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 compact and front-loaded. The first sentence states the purpose and return fields, and the second and third sentences add source and failure behavior. Every sentence earns its place with no filler.

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?

Given the tool's low complexity, one optional parameter, and read-only annotations, the description is nearly complete. It covers the return fields, default network, source, and null-failure behavior. The only minor gap is that it does not specify units or types for fields like 'seconds remain' or 'how far into the epoch,' but the absence of an output schema makes this acceptable.

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 compensate for parameter meaning. It does mention 'Flare (default) or Songbird,' which reinforces the network parameter's allowed values. However, this largely duplicates the schema's default and pattern, and no extra semantics such as validation behavior or edge-case handling are provided.

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 uses a specific verb ('Return') and identifies a precise resource: 'FTSO reward-epoch state' for Flare or Songbird. It lists the exact fields returned, making its purpose unmistakable and clearly distinct from sibling getter tools like get_network_economics or get_chain_activity.

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 implies when to use the tool: when the agent needs current FTSO reward-epoch state such as epoch ID, start time, progress, and seconds remaining. However, it does not explicitly state when not to use it or name alternative tools for related but different network status queries.

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