supercoach_leagues

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true. The description adds 'Auth: none needed', notes these are 'public/featured' leagues, and spells out the return shape, going beyond the annotation baseline.

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?

The description is compact and information-dense: purpose, return shape, example, and auth in a minimal number of sentences. Every line earns its place.

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 description covers purpose, usage, return fields, example, and auth; combined with rich schema and annotations, it is sufficient for an agent to invoke this tool. Minor omission: does not mention whether the list is exhaustive or if there are any limits, but the openWorldHint covers extensibility.

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 covers all parameters with detailed descriptions (e.g., mode, year calendar nuance, sport options), and the description does not add additional parameter semantics beyond the schema. Baseline 3 applies due to high schema coverage.

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 clearly states it returns 'public/featured leagues for one sport+season+mode' and enumerates the fields returned, which distinguishes it from sibling tools like supercoach_players or supercoach_teams. The phrase 'Useful to discover competition_ids and the league types on offer' further anchors its specific 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?

Gives a clear use case ('Useful to discover competition_ids and the league types on offer') but does not explicitly discuss alternatives or exclusions. It implies when to use but doesn't compare to other SuperCoach tools.

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