Get a MaxPreps school profile

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

The annotations already provide readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is covered. The description adds the content inventory and path provenance, but no additional behavioral details such as error handling, rate limits, or the conditional nature of includeNearby.

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 short sentences, front-loaded with the profile summary and followed by the essential usage instruction. Every word earns its place with no redundancy beyond the harmless 'Read-only' echo of the annotation.

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 expected profile contents and identifying the required input source. The only small gap is that 'nearby schools' is described as part of the profile while the includeNearby parameter governs whether it appears, but the schema resolves this ambiguity.

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 coverage is 100%, so the parameters are already documented; the description adds value by telling the agent where to obtain the school path ('Take the path from maxpreps_search'). It does not connect includeNearby to the 'nearby schools' mention, but the schema handles that.

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 identifies the resource as a school profile and enumerates its contents (identifiers, location, state athletic association, partner flags, nearby schools, articles/videos). This distinguishes it from team-level siblings, though it does not explicitly contrast with maxpreps_get_team or similar tools.

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?

'Take the path from maxpreps_search' provides a direct usage instruction: obtain the required school path from a prior search. This establishes a clear workflow without explicitly naming alternative tools or exclusions, so it is strong but not maximal.

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