standings

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds only the 'my row flagged' behavior, and the dangling 'Demo league: a message.' fragment suggests a demo/fallback mode without explaining it, so it contributes little usable behavioral context.

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 fragments, the second of which ('Demo league: a message.') is truncated and unparseable, so a meaningful share of the text earns no place. The useful scoping detail is front-loaded, which is the only structural positive.

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?

There is no output schema and no parameters, so the description must carry the full burden for a simple read tool, yet it leaves the demo-league behavior unexplained and does not say what the returned standings contain or how 'my row' is marked. For a no-schema tool this is under-specified.

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?

With zero parameters the baseline is 4, but the description invokes 'mine=true' as if it were an input, which contradicts the empty schema and may mislead the agent into trying to pass a parameter. That phantom-parameter reference pulls it below baseline.

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 first clause states a clear verb+resource (Yahoo league standings) and adds a scope detail (my row flagged). But the trailing fragment 'Demo league: a message.' is truncated and conveys nothing, and the '(mine=true)' notation implies a parameter that does not exist in the schema, muddying rather than sharpening the purpose.

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 guidance on when to use this versus close siblings like league_overview, scoreboard, rankings, or league_profile. The agent must guess whether standings is the right call for a standings question or whether one of the other overview tools supersedes it.

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