pinnacle_league_matchups

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

No annotations are provided, so the description carries the full burden. It discloses the return format (array of objects with specific fields), which is transparent about output structure. However, it does not mention any authentication requirements, rate limits, or potential side effects (though likely read-only).

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 short and efficient: one line for purpose, one line for return structure. The example (NBA) adds clarity. However, the return format could be formatted more readably (e.g., using bullet points).

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 the return format, which is helpful. But it lacks context on how to resolve leagueId, whether pagination exists, or if there are any limits on the number of matchups. For a simple tool, it is adequate but not thorough.

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 0%, so the description must compensate, but it only says 'one league (competition)'. It does not explain what the leagueId parameter represents (e.g., how to obtain it, valid ranges, or if it corresponds to a specific API). This leaves the agent with insufficient guidance to correctly provide the parameter.

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 returns 'all matchups for one league' with a concrete example (NBA game). It distinguishes from siblings like pinnacle_league_matchups_live and pinnacle_matchup by specifying the scope is all matchups for a league.

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 needing all matchups for a league via the required leagueId, but lacks explicit guidance on when not to use it or alternatives. For example, it doesn't mention pinnacle_sport_matchups for filtering by sport or pinnacle_league_matchups_live for live-only data.

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