Get a MaxPreps school profile

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint. The description adds 'Read-only' (redundant with annotation) and the input dependency on a search path, plus the specific content returned (nearby schools, articles/videos). This provides useful behavioral context beyond the structured 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 two sentences, front-loaded with the primary purpose and details, and includes a direct usage hint. Every word earns its place with no filler or repetition.

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 appropriately lists the main content groups of the profile. It also specifies the required input origin. It could mention error handling or exact field details, but for a read-only profile tool with simple parameters, it is largely complete.

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?

Both parameters are fully described in the schema (100% coverage), so the baseline is 3. The description adds extra meaning by tying the 'school' parameter to 'maxpreps_search' and mentioning 'nearby schools' for the includeNearby flag, which reinforces how to use them.

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 ('School profile') and lists its components (identifiers, location, state athletic association, partner flags, nearby schools, recent articles/videos). This distinguishes it from sibling tools like maxpreps_get_team and maxpreps_get_athlete, which target different entities.

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 instructs users to 'Take the path from maxpreps_search', providing explicit guidance on how to obtain the required input. It does not explicitly exclude alternatives or state when not to use the tool, but the context is clear.

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