get_schedules_by_team_id

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

With no annotations, the description must fully convey behavioral traits. It discloses the scope ('all active seasons') but omits details like pagination, rate limits, or error handling. It is adequate but lacks depth for a tool with 5 parameters and no output schema.

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, clear sentence of 12 words. It efficiently states the main action and scope without redundancy. Every word contributes value.

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 could clarify the return format or constraints (e.g., 'complete schedule' meaning all matches?). It also doesn't leverage the include/select/filters parameters to clarify behavior. Adequate but not comprehensive for a tool with 5 parameters.

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% coverage (all 5 parameters have schema descriptions). The tool description adds no additional meaning beyond 'team_id' being required. It does not explain how include, select, filters, or locale affect results, leaving the schema to bear the full burden.

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?

Description clearly states the tool's action: 'Get the complete schedule for all active seasons of a team.' It specifies the resource (schedule) and scope (all active seasons), distinguishing it from sibling tools like get_schedules_by_season_id or get_schedules_by_season_and_team.

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?

No explicit guidance on when to use this tool versus alternatives. The phrase 'all active seasons' implies it covers multiple seasons, but there is no mention of when to prefer this over get_schedules_by_season_id (specific season) or get_schedules_by_season_and_team. Usage context is implied rather than stated.

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