espn_rankings

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

With no annotations provided, the description carries the full burden. It discloses useful behavioral context: the data comes from ESPN's 'credential-free public JSON' (no auth needed) and rankings exist only for college leagues. It does not mention rate limits, pagination, freshness, or response shape, but for a simple read-only rankings fetch those are minor gaps rather than serious omissions.

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 sentences, front-loaded with the core purpose ('Returns poll rankings') followed by the scope constraint. No filler. The only minor inefficiency is the second sentence re-listing enum values that already exist in the input schema, making it somewhat longer than necessary, but overall it remains compact and well organized.

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?

For a simple 2-parameter read-only tool with full schema coverage, the description is largely complete: it explains what is returned, the source, and the valid input domain. Gaps are minor — no output schema exists and the description doesn't hint at response structure or pagination — but an agent can select and invoke this tool correctly based on what is provided.

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 coverage is 100% with both parameters fully documented and enumerated, so the baseline is 3. The description adds some value by explaining why the enums are restricted ('rankings are only published for college leagues') and by mapping sport to league, which the terse schema entries ('Sport key', 'College league key') do not convey. Still, it largely restates the enum values already present in the schema.

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 and resource: 'Returns poll rankings (e.g. AP Top 25) for a college league'. The example (AP Top 25) and the college-league restriction make the scope concrete and distinguish it functionally from ESPN siblings like espn_scoreboard, espn_standings, and espn_team_roster. However, it does not explicitly name a sibling it is not, so it stops short of full differentiation.

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 usage context via 'Rankings are only published for college leagues' — a useful exclusion that tells the agent this tool is not for pro leagues. But it never states when to prefer this over alternatives such as espn_standings or espn_scoreboard, nor does it name any alternative. Usage guidance is implied rather than explicit.

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