get_schedule

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

No annotations provided, so description must disclose behavioral traits. It does not mention that the tool is read-only, not destructive, or any potential side effects. The description is minimal and lacks safety information.

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 very short (8 words) but is a fragment ('Team upcoming schedule') rather than a complete sentence. It is front-loaded but could be more structured. Every word earns its place, but the fragment reduces clarity.

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 2 unannotated parameters and no parameter descriptions, the description does not fully equip an agent to invoke the tool correctly. While output schema exists, the description lacks detail on date range, return format, or how days_ahead interacts with the schedule. Completeness is low.

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 description must add meaning. It clarifies that 'team' can be name or ID and that 'days_ahead' defaults to 7, but does not explain the meaning of 'days_ahead' (e.g., from today?) or the format of team identifiers. Missing details limit effective parameter use.

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 states it returns 'Team upcoming schedule' and specifies it accepts team name or ID. The purpose is clear but could be more explicit about the verb (e.g., 'Retrieves'). It does not differentiate from sibling tools like 'get_game_details' or 'get_team_advanced_stats'.

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 guidance on when to use this tool versus alternatives. The description only mentions it accepts team name or ID, but does not explain context or prerequisites. An agent would need to infer usage.

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