Get a MaxPreps team season

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

The readOnlyHint, openWorldHint, and idempotentHint annotations already cover the safety profile, and the description repeats 'Read-only' without adding new behavioral details. It does add useful scope context—one season and roughly 20 years of seasons—but no auth, rate-limit, or failure-mode disclosure.

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, front-loaded with the core output content and a clear use case. Every sentence earns its place without redundancy.

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?

With no output schema, the description compensates by listing the key returned fields: identifiers, record, points, standing, rankings, and season list. Combined with the complete input schema and clear read-only annotations, an agent has enough to select and call this tool correctly.

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%, so the schema already explains team, season, and includeSeasons. The description adds no parameter-level meaning beyond the schema, so the baseline of 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 names the exact verb and resource: a team season overview, including identifiers, record, points for/against, standing, rankings, and the full season list. This clearly differentiates it from siblings like maxpreps_get_schedule, maxpreps_get_standings, and maxpreps_get_rankings.

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?

It gives a concrete intended use: confirm a record without summing a schedule, which routes agents away from maxpreps_get_schedule. It does not explicitly enumerate when to prefer it over roster, rankings, or other sibling tools, but the use case is clear.

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