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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety and determinism are covered structurally. The description adds genuine context beyond that by disclosing the data source ('Federal') and that part of the payload is a derived estimate rather than raw reporting. It says nothing about data vintage, coverage gaps, or caching, so it is useful but not rich.

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?

A single front-loaded sentence that leads with the resource and then enumerates payload contents, with the differentiator ('No student profile needed') placed last. Every clause carries retrieval-relevant content and there is no filler.

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 correctly compensates by listing the return fields, which is the key completeness requirement here. The remaining gap is metadata about the data itself — reporting year, whether every U.S. college is covered, and how the GPA/SAT chance estimate is derived.

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% and there is a single required 'school' string, so the schema already carries the parameter burden. The description only clarifies that no student profile input is required, which is mild added meaning; it offers no guidance on name format (e.g., full name vs. campus/ID).

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?

Names a specific verb (get) and resource (federal admissions and outcome data for one U.S. college) and enumerates the exact fields returned: applicants, admits, yield, SAT/ACT middle 50%, test policy, cost, net price, graduation rate, earnings. The closing clause 'No student profile needed' implicitly separates it from estimate_admission_chances, so an agent can route without opening the schema.

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?

Gives a clear usage condition: use this when you want a school's aggregate data and have no student profile. It does not explicitly name or exclude alternatives (estimate_admission_chances, search_colleges, find_colleges_for_score), so the when-not side is left to inference.

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