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

With no annotations, the description carries the burden and it does disclose concrete behavior: daily cadence, live-league condition, merkle commitment, and off-season dormant reporting instead of stale numbers. This goes well beyond a generic getter, though it stops short of covering error cases or data volume limits.

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?

Two dense sentences with no filler, front-loading the main output before adding provenance and off-season behavior. The second sentence's blockchain registry detail is niche but earns its place as behavioral context.

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?

The tool is simple and has an output schema, so return details don't need description. But the missing parameter semantics and lack of sibling differentiation leave gaps an agent must resolve before confident invocation.

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 needed to explain both parameters. It only tangentially links 'league' via 'per live league' and says nothing about 'limit', its default, or the meaning of an empty string.

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 identifies the resource as a daily sports movers board for hot, high-volume players per live league, which distinguishes it from siblings like get_forecast or get_market_snapshot. However, it lacks an explicit verb like 'returns' or 'lists', so it reads more like a product label than a clear operation.

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 use when daily sports movers are needed and mentions live leagues, but it never states when to prefer this over sibling tools or names any alternatives/exclusions. An agent must infer the use case from the noun phrase 'daily sports movers.'

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