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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile is covered. The description adds that results carry country and university counts, which is useful return-content context, but it says nothing about pagination despite limit/offset parameters existing.

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 with no filler. It is tight, but the compression comes at the cost of omitting routing and parameter detail rather than by economizing on redundancy.

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?

An output schema exists, so return values need not be restated, and annotations cover safety. However, for a four-parameter search tool inside a 21-tool family with zero schema documentation, the description leaves both filtering semantics and sibling choice unresolved.

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 description coverage is 0% across four parameters (query, limit, offset, country_code), so the description must compensate and largely does not. "Country and university counts" faintly suggests a country dimension, but no parameter's meaning, matching behavior, or default handling is clarified.

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?

Specific verb+resource ("Search cities") with a stated data scope: the active university catalog and public room listings. It implicitly separates itself from search_universities and search_rooms by naming the entity it returns and where it draws from, though it never names those siblings directly.

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 only usage cue is the trailing "for assisted room search," which implies a discovery step before a room search but states no when/when-not condition or alternative. With search_rooms, search_universities, and list_search_metadata available, an agent gets no routing help.

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