get_schedule

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

With no annotations provided, the description carries the burden of behavioral disclosure. It discloses that the schedule includes past results and upcoming games, which is useful scope information, but it does not mention return format, data freshness, or read-only behavior beyond the obvious.

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 10 words, front-loaded with the action ('Get') and resource ('a team's schedule'). Every word adds value, with no redundancy or filler.

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?

For a simple read tool with two parameters and no output schema, the description sufficiently explains the tool's purpose and returns (past results and upcoming games). It could mention league or team scoping, but those are already in the schema, and the sibling context helps clarify. Slightly incomplete regarding data boundaries like season or competition, but acceptable.

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% for both parameters, so the schema already explains 'team' and 'league'. The description does not add extra meaning beyond noting the team's schedule, but it does not need to since the schema is complete.

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 uses a specific verb ('Get') and resource ('a team's schedule'), clearly distinguishing it from sibling tools like get_standings or get_scoreboard. The phrase 'including past results and upcoming games' adds precision about the content.

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 for retrieving a team's schedule but does not explicitly mention alternatives or when not to use this tool. It provides clear context but lacks explicit exclusions or references to sibling tools like get_game for single games.

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