espn: Get standings

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, so the safety and caching profile is covered structurally. The description usefully adds what the payload contains (conference/division grouping, records, rankings), but says nothing about pagination, whether a season must be supplied, or coverage limits across sports.

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 compact sentences with the verb/resource front-loaded and the return shape immediately after; no filler. Could arguably be tightened further but there is no wasted text.

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 at least sketches the return shape, which is valuable. Combined with a fully documented 5-parameter schema and read-only annotations, this is nearly complete; only sport coverage and season requirements go unstated.

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%, so the schema fully documents sport, league, group, fields, and season with examples. The description adds no parameter-level meaning (e.g., that group maps to a conference/division filter), so the baseline 3 applies.

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?

States a specific verb and resource ("Get league standings") and then enumerates the return content (conference/division standings with records, win/loss, ranking). It does not, however, distinguish itself from the many other standings siblings (nhl_get_standings, mlb_get_standings, sportsdb_get_standings, f1_get_driver_standings), leaving the agent to infer the ESPN multi-sport scope from the name prefix alone.

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?

No when-to-use guidance is given. The description never says how this differs from the ~8 other standings tools in the sibling list, nor when a sport-specific standings tool should be preferred over this generic ESPN one. The agent must guess from the name.

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