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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is covered without prose. The description adds only 'Public profile', implying no auth, and an enumeration of returned fields; it says nothing about pagination, rate limits, or error behavior for invalid ids. 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?

A single front-loaded sentence with the core purpose first, followed by the field inventory. No filler sentences; the field list earns its place because no output schema exists.

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 and one fully-documented parameter, the description supplies exactly what is missing: the shape of the returned profile (university, city, address, website, about, highlights, courses with fees, counts, profile url). An agent knows what it will get back.

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 the single parameter is already documented as 'College id', so the baseline is 3. The description adds meaning beyond the schema by specifying where valid ids come from ('from search_colleges') and that the value is a numeric 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?

Specific verb+resource: 'Public profile of one college by id', which is immediately distinguishable from the sibling search_colleges. It also names the source of the id ('from search_colleges'), so an agent can tell this apart from the list/search tool without opening either 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?

The parenthetical '(from search_colleges)' effectively tells the agent when this tool applies: after obtaining a college id from a search. There is no explicit when-not guidance or named alternative for the reverse case, but the retrieval context is clear.

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