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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, covering safety. The description adds the premium API cost and the specific fields returned, which is useful but does not mention response format, error handling, or rate limits. The cost disclosure is a behavioral addition beyond annotations, but overall the description does not substantially expand on the behavioral profile given that annotations already cover the key traits.

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 concise sentence that states the action, the resource, and the key output fields, followed by a cost note. It is front-loaded with the primary purpose and contains no redundant or filler text. Every word adds value.

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 lists the expected data categories (location, type, enrollment, accreditation, notable programs, key statistics), giving the agent a good idea of what the response will contain. It does not specify the exact structure (e.g., JSON format) or mention fuzzy matching or required formatting for the lookup, but for a simple one-parameter tool this is largely sufficient. A 4 reflects that it is mostly complete but could include details on response structure or matching behavior.

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 100%: the schema clearly states the parameter is a 'University or college name' with an example. The description does not add any extra detail about parameter formatting, matching behavior, or acceptable values. Per the rubric, with high schema coverage, the baseline is 3, and the description offers no added value for the parameter.

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 uses a specific verb 'retrieve' and a clear resource 'university or college', and lists the exact data fields (location, type, enrollment, accreditation, notable programs, key statistics). This is distinct from any sibling tool, as no other tool in the list pertains to universities. The purpose is unambiguous and fully specified.

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 makes the context obvious: it is for retrieving university/college information. However, it does not explicitly mention when not to use it or name any alternative tools. Since the tool is unique among siblings, the context is clear, but there is no explicit guidance on exclusions or alternatives, which would merit a 5.

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