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

With no annotations provided, the description carries the transparency burden. It discloses that the tool is public (no auth required) and that it returns admissions stats and AdmitBase links, which is useful behavioral context. However, it doesn't mention any rate limits, pagination behavior, or whether results are sorted, but for a simple search tool this is reasonably transparent.

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 with the main action front-loaded. The first sentence specifies the search criteria, the second describes the return value and public access. Every word is useful, no fluff 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?

Given no output schema and no annotations, the description adequately explains the purpose, parameters (via context), and return type. It doesn't explain every edge case like result sorting or exact output structure, but for a search tool that returns stats and links, it's sufficiently complete. Minor gap: no mention of default limit or possible result formats, but the schema handles limit defaults.

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% with each parameter having a description. The description adds a general mapping by mentioning 'by program type, name, or ranking range' which correlates with program, query, and ranking parameters, but it doesn't provide additional semantics beyond what the schema already says. This aligns with the baseline of 3 for high schema coverage.

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 verb 'Search' and the resource 'professional schools' with specific filters (program type, name, ranking range), distinguishing it from sibling tools like get_school_stats by focusing on search/filter behavior and return of admissions stats and AdmitBase links.

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 implies usage context: you use this when you need to find schools by program, name, or ranking. It doesn't explicitly exclude alternatives, but the sibling tools have obviously different purposes (e.g., calculate_match_score, compare_to_applicants), making the context clear. No explicit when-not-to-use is given, so not a 5.

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