Get one college's full record

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

No annotations provided. Description adds some behavioral context (accepts plain name and slugifies it), but lacks disclosure of error handling or output format beyond listing fields.

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 sentences: first sentence lists data fields concisely; second sentence adds slugification behavior and sibling tool reference. No fluff.

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?

Simple tool with one param and no output schema. Description covers input flexibility and enumerates output fields. Missing error behavior but overall adequate.

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 covers 100% of one parameter with a basic description. Description enhances by providing example slug format and stating it can also accept a plain name, adding clarity beyond the schema.

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?

Description explicitly states it retrieves the full record for one college by slug, listing specific data fields. It distinguishes from sibling 'search_colleges' which is for discovering slugs.

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?

Clearly explains when to use (need full record for a specific college by slug) and when to use alternative (use search_colleges to discover slugs). Also notes it can accept a plain name and slugify it.

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