get_player_all_leagues

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

With no annotations, the description carries the burden. It mentions returning a per-league stats block with canonicalUrl and gracefully omitting missing leagues. This is adequate but doesn't detail auth, rate limits, or performance.

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 two sentences, front-loaded with the core purpose and examples, then usage guidance. No redundant information.

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 tool is simple with one param and no output schema. The description covers what is returned (per-league stats block, canonicalUrl) and behavior (omits missing leagues). Slight lack of detail on stats format, but sufficient for selection.

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 100% with one parameter, playerSlug. The description adds value by explaining the slug format and suggesting to use search_players first, which goes beyond the schema description.

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 the tool retrieves a player's statistics across multiple CricketStudio leagues in one call, listing specific leagues (IPL, MLC, WPL, etc.). This distinguishes it from per-league sibling tools like get_bbl_player_profile or get_player_profile.

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 states 'Use for players who appear in multiple leagues' and provides examples. It lacks explicit when-not-to-use instructions, but the sibling tools for individual leagues imply the alternative.

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