Get raw MaxPreps page data

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, so the description only needs to add behavior beyond those. It discloses that positional payloads arrive as bare arrays with no field names, that roster rows are always projected to public roster fields, and that data is raw and undecoded. This is valuable behavioral context not present in the 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?

The description is compact and front-loaded with the core escape-hatch purpose, followed by usage guidance, payload caveats, and projection details. Every sentence contributes information, with no filler or repetition of the title beyond necessary context.

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 raw page fetch tool with no output schema, the description sufficiently explains what the agent will receive (raw, undecoded, sometimes bare arrays) and how to route to specialized tools when needed. It also covers the read-only nature and roster projection, leaving no critical gap for an agent deciding whether and how to invoke the tool.

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 documents both path and keysOnly. The description adds context for path by mentioning 'any public MaxPreps page' and 'undecoded,' but it does not add new meaning for keysOnly. The baseline of 3 is appropriate because the schema carries the parameter documentation 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?

The description opens with 'Escape hatch: return the raw server-rendered data for any public MaxPreps page, undecoded,' which gives a specific verb, resource, and scope. It also explicitly differentiates from dedicated siblings by noting when the general page tool is needed and by naming maxpreps_get_roster / maxpreps_get_schedule for roster and schedule payloads.

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 provides direct usage guidance: 'Use when a dedicated tool does not cover what you need' with concrete examples (playoff brackets, conference standings, article listings). It also tells the agent to use maxpreps_get_roster / maxpreps_get_schedule for positional payloads, making the alternative selection explicit.

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