Compare Universities

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

Annotations include readOnlyHint=true and openWorldHint=false, and the description does not contradict them. It adds context by stating metrics are 'verified' and 'local' and may be unavailable ('when available'), which informs partial-result behavior. However, it does not explain what happens if metrics are missing or how results are structured, so it adds moderate value beyond the annotations.

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 a single sentence, front-loaded with the verb 'Compare', and every word contributes meaning. 'when available' is a useful qualifier, not filler, making it highly concise and well-structured.

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?

Despite the tool's simplicity, the description leaves out critical invocation details. There is no output schema, so the description should explain what the comparison result looks like, but it doesn't. It also lacks parameter semantics and usage context, making it insufficient for an agent to invoke correctly in many situations.

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?

The schema has two array parameters with no descriptions and 0% coverage. The description does not explain what 'indicators' or 'university_names' should contain, their format, or any constraints. The property names give a superficial hint, but the description fails to add meaningful parameter semantics.

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 'Compare' and the resource 'universities', with an implied scope of multiple universities. It differentiates from siblings like get_university_metrics (singular focus) and search_university (search), but the phrases 'verified local metrics' and 'when available' introduce some ambiguity about what exactly is being compared.

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?

No guidance is provided on when to use this tool versus alternatives like get_university_metrics or explore_universities. There are no exclusions or context that would help an agent decide between comparable tools, so the usage is only implied by the name.

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