sm_leagues

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It adds useful context by explaining 'live' as 'leagues currently in play' and noting the return purpose. However, it does not disclose behavior around pagination, optional include expansions, or how modes map to required parameters beyond the mode names, leaving some behavioral aspects untold.

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 only two sentences, front-loaded with the core purpose. The mode list is compact and informative, and every word earns its place. No redundant fluff or repetition of schema field names.

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 the tool has 7 parameters, 6 modes, no output schema, and no annotations, the description covers the basic purpose and mode taxonomy but omits details about pagination (page), include expansion, parameter combined usage, and typical response structure beyond mentioning league IDs. It is sufficient for simple use but not fully complete for a multi-mode 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 description coverage is 71%, which is moderate. The description enhances parameter understanding by correlating modes with parameters: 'by_id' implies id, 'by_team' implies teamId, 'by_country' implies countryId, and 'search' implies searchQuery. This adds meaning beyond the plain schema property descriptions, though it does not explain 'page' or 'include' semantics.

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 'Get football leagues' with a specific verb and resource. It further enumerates distinct modes ('all', 'by_id', 'live', by_country', 'by_team', 'search'), which distinguishes it from sibling tools like odds_get_sports that focus on sports or sm_livescores on live scores. The note about returning league IDs for other endpoints clarifies its role as a prerequisite tool.

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 by listing modes and stating league IDs are needed for other endpoints, but it does not explicitly say when to use this tool versus alternatives or provide exclusionary guidance. For example, it does not mention that to get scores, one would use sm_livescores. The context is clear but lacks explicit 'when-to-use' or 'when-not-to-use' statements.

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