supercoach_leagues

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

No annotations are provided, so the description carries full burden. It implies a read-only operation by listing return fields, but does not explicitly state non-destructiveness, authentication needs, or performance characteristics. The description is adequate but lacks deeper 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?

The description is three sentences long, front-loaded with the core purpose, and includes a useful example and return structure. Every sentence adds value without 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?

Given no output schema, the description provides a detailed return structure and example. It covers the essential aspects of the tool for a league listing. Minor gaps exist (e.g., no parameter format details), but overall completes the necessary context for a simple tool.

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 0%, so the description must compensate. It mentions 'one sport+season+mode' and provides an example ('AFL classic leagues') that maps to sport and mode. However, it does not explain the exact formats or allowed values for parameters, leaving some ambiguity.

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 it returns public/featured leagues for a sport+season+mode, lists the fields returned, and gives an example. It clearly distinguishes from sibling supercoach tools (player, players, real_fixture, settings, teams) by focusing on leagues.

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 explicitly says it is 'Useful to discover competition_ids and the league types on offer,' which gives a clear usage hint. It also provides an example for AFL classic leagues. However, it does not mention exclusions or alternatives, but as the only league tool among siblings, this is sufficient.

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