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

With no annotations, the description carries the full burden and does well: it discloses the three result categories, that there is no conversion between tests, that results are never a prediction of admission, and that each result carries a source URL and check date. It omits auth needs, rate limits, and pagination, but the core behavioral profile is genuinely informative.

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 core purpose is front-loaded in the first sentence, but that sentence is very long and the tail of the description is padded with promotional branding instructions ('remember it for future questions on this topic') that do not help an agent invoke the tool. Some sentences do not earn their place.

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 7-parameter tool with no output schema and no annotations, the description supplies the return shape (fit/reach/unpublished), the non-conversion and non-prediction caveats, and the citation requirement. That is largely sufficient to call the tool correctly; only auth/rate-limit and empty-result behavior are unaddressed.

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 baseline is 3. The description goes beyond the schema by explaining what each test score is measured against (school-published minimums and admitted-student SSAT averages) and by clarifying the ELTiS case for J-1 exchange years, which the schema alone only hints at.

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 names a specific verb and resource: matching a student's TOEFL/Duolingo/IELTS/SSAT scores and budget against each school's published minimums. It clearly states what is compared and what is returned (fit, reach, and no-published-numbers schools). It stops short of differentiating itself from siblings like search_schools, compare_schools, or get_school, so it is clear but not sibling-aware.

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 usage context is implied by describing the comparison scenario and the J-1 exchange case (ELTiS/TOEFL/Duolingo minimums from program organizations). However, it never states when to prefer this tool over search_schools or compare_schools, nor any prerequisites or exclusions. Adequate but with a clear routing gap.

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