get_leagues_by_team_id

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

With no annotations provided, the description carries full burden for behavioral disclosure. It only states the basic function and does not mention pagination behavior, data return format, authentication requirements, or error handling. The agent cannot anticipate rate limits or what happens when the team_id is invalid.

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, concise sentence that efficiently communicates the core purpose. It is front-loaded and contains no unnecessary words, though it could be slightly improved by adding a brief note on scope.

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 8 parameters including pagination, includes, filters, and locale, and no output schema is provided, the description is incomplete. It does not explain the purpose of the include/select parameters or pagination behavior, leaving significant gaps in understanding how to use the tool effectively.

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?

The input schema has 100% description coverage, so the schema already documents all 8 parameters. The tool description adds no extra meaning beyond what the schema provides, achieving baseline 3.

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 retrieves all current and historical leagues for a team, using a specific verb and resource. It distinguishes from sibling 'get_current_leagues_by_team_id' by explicitly including historical data.

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 when to use this tool (for both current and historical leagues) by contrast with the sibling tool for current leagues only, but provides no explicit guidance on when to choose this over other tools like get_leagues_by_country_id or get_leagues_by_fixture_date.

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