Get raw MaxPreps page data

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

Beyond the readOnlyHint/openWorldHint/idempotentHint annotations, the description adds critical behavioral context: the data is 'undecoded', and 'positional payloads — team rosters and schedules — arrive as bare arrays here with no field names'. It also clarifies that this works for 'any public' page, which is useful for setting expectations.

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 key phrase 'Escape hatch'. It contains only three sentences, each providing distinct value: purpose, usage guidance, and a specific caveat. There is no redundant or filler content.

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 an escape-hatch tool with only two well-documented parameters and no output schema, the description covers the essential context: what it does, when to use it, how the raw data behaves, and when to prefer other tools. The openWorldHint and readOnlyHint annotations complement this, making the tool's behavior sufficiently clear for an agent.

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 already provides full descriptions for both parameters (path and keysOnly) with 100% coverage, so the baseline is 3. The description adds general context about the raw output format (undecoded, bare arrays) but does not directly elaborate on how to use the parameters beyond what the schema already states.

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's function: 'return the raw server-rendered data for any public MaxPreps page, undecoded.' It also distinguishes itself from sibling tools by presenting itself as an escape hatch for cases not covered by dedicated tools and explicitly redirects roster/schedule needs to maxpreps_get_roster / maxpreps_get_schedule.

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?

Provides explicit when-to-use guidance: 'Use when a dedicated tool does not cover what you need' and lists examples like playoff brackets, conference standings, and article listings. It also clearly states when not to use it (for rosters/schedules), naming the alternative tools.

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