Games Get Power Index

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

The annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds only that the payload contains FPI/BPI ratings and efficiency metrics, with no mention of coverage, freshness, or rate limits, so added value beyond structured data is modest.

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?

A single front-loaded sentence naming the verb and the exact metrics returned. No filler, no redundancy.

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 is the only place return content can be characterized, and it does indicate the metric families (FPI/BPI, efficiency). It does not say what entities or granularity come back (per team? per league? sorted how?), which leaves a modest gap for a read tool with three parameters.

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 100%: sport, league and season are each documented in the schema, including the season-year convention. The description adds no parameter-level meaning, which is the expected baseline when the schema already does the work.

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 gives a specific verb ('Fetch') and resource ('league team power index (FPI / BPI) ratings and efficiency metrics'), so an agent knows it returns analytic power ratings rather than raw records. It does not name or distinguish itself from plausible siblings such as games_get_rankings or games_get_game_predictor, so the differentiation is implicit at best.

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?

There is no statement of when to choose this tool over the many other league-level siblings (standings, rankings, predictors, futures). Usage is only inferable from the resource name, and with 30+ sibling tools the absence of any routing guidance is a real gap.

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