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

Annotations already communicate readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the safety profile is well covered. The description adds the returned attributes but not behavioral details like pagination or result ordering; with annotations present this is adequate 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?

Two front-loaded sentences cover the search dimensions and return fields with no filler. Every phrase contributes useful information an agent needs to select and invoke the tool.

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 read-only search tool with fully documented optional parameters and safety annotations, the description is nearly complete: it states the domain, filters, and returned data. The main gap is explicit routing among the many college_* siblings, and there is no output schema, though the described return fields mitigate that.

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?

All six parameters already have descriptions in the schema, giving 100% schema description coverage, so the baseline is 3. The description only restates the same criteria names and does not add format or interaction details beyond what the schema already provides.

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 opens with a specific verb and resource ('Search US colleges and universities') and enumerates filter dimensions like name, state, control type, size, and accreditor, so the core purpose is clear. It does not explicitly differentiate from sibling tools such as college_accreditation or college_compare, so the agent must infer the boundary from names.

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 gives clear context for when to use the tool: finding institutions that match various institutional attributes. However, it does not state when not to use it or name an alternative among the many college_* siblings.

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