Get the all-school schedule

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint. The description adds meaningful context beyond these: it returns a window of ~10 upcoming events, ordered oldest first, and is not a complete season. This is valuable behavioral information not present in annotations.

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?

Two sentences: the first states the core function, the second adds the critical window caveat and alternative. No filler, information is front-loaded, and every sentence earns its place.

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?

The description is adequate for this simple list tool: it explains the window limitation, ordering, and directs to the alternative for full season. It does not describe the return event structure or pagination, but given there is no output schema and the tool is straightforward, this is a minor gap. The year parameter is fully documented in the schema.

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 covers 100% of the single parameter (year) with a rich description including examples, default behavior, and past season handling. The tool description does not add parameter details, but the schema already provides full semantics, so baseline 3 is appropriate.

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 the tool returns 'Upcoming events across every team, oldest first', which specifies the verb (get), the resource (all-school schedule/events), and the scope (every team). It distinguishes from the sibling tool mpaz_get_team_schedule by explicitly noting this covers all teams, not a single 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?

The description provides explicit guidance: it is for upcoming events across all teams, and it directly names the alternative tool mpaz_get_team_schedule for a team's full season. It also warns that this returns only a window, not the whole season, which helps the agent choose correctly.

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