get_my_leagues

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

No annotations are provided, so the description must convey behavioral traits. It only states the functionality (read-only get) but does not disclose authentication requirements, rate limits, or whether the response is paginated. This is minimal for a tool with no annotations.

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 a single sentence of 9 words, highly compact and front-loaded. It efficiently conveys the core purpose but could be slightly expanded to include parameter guidance without becoming verbose.

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 and two optional params, the description covers the main behavior adequately but does not explain return structure or disambiguation from similar tools (e.g., get_my_leagues vs get_leagues_by_country_id). It is minimally complete.

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%, meaning the JSON schema already describes the 'include' and 'locale' parameters. The description adds no further meaning or hints about their usage or accepted values, so it meets the baseline but adds nothing extra.

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 all leagues available within your current subscription,' specifying the verb (Get), resource (leagues), and scope (subscription-based). This distinguishes it from sibling tools like get_all_leagues which likely returns all leagues globally.

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 use when the user wants their subscribed leagues, but no explicit when-not or alternatives are mentioned. Among many sibling tools for leagues, this lacks guidance on when to choose this over get_leagues_by_country_id or get_all_leagues.

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