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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety and determinism profile is fully covered by structured data. The description's contribution is the content inventory of the returned profile, which is useful but strictly about payload rather than behavior. It says nothing about what happens with an unknown slug, missing data, or truncation of review excerpts.

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?

One sentence, front-loaded with the resource and scope, followed by a compact enumerated list of returned fields. No filler, no repetition of the title, and the most decision-relevant information (single college, full profile) comes first.

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 carries the burden of describing the return payload, and it does so thoroughly for a directory-profile tool. Safety behavior is covered by annotations. The remaining gap is edge-case behavior (invalid or delisted slug, empty fields), which is minor for a read-only lookup.

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?

There is a single required parameter and schema description coverage is 100%; the schema already supplies the pattern, length bounds, and the "College slug, e.g. from search results" note. The description adds no further meaning about slug format or lookup semantics. Baseline 3 is appropriate when the schema does all the work.

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 gives a specific verb-scope plus resource ("Full public profile of one college or university") and enumerates exactly what the profile contains: approvals, NIRF rank, rating, fees, placements, courses with fees, reviews, FAQs. That is far more concrete than a generic "get college details." It does not, however, name or contrast itself with siblings such as search_colleges or get_college_course_details, so the distinction is only implied.

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 contains no when-to-use, when-not-to-use, or alternative-tool guidance. The only workflow hint, "College slug, e.g. from search results," lives in the input schema, not the description, and it is a weak pointer at best. An agent must infer that this is the detail-expansion step after search_colleges.

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