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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile needs no restatement. The description does add one genuine behavioral detail — that merit is the 'latest published Category A closing merit' with an accompanying year, implying data staleness semantics — but it mostly enumerates return fields, which an output schema already covers. No pagination, rate-limit or sorting-behavior disclosure.

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?

Three compact sentences with zero redundancy: trigger first, return contents second, exclusions last. Every clause carries routing or scope information.

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?

An output schema exists, so return values need not be explained in depth, and annotations cover the safety profile. For a single-optional-parameter read-only list tool, the description supplies everything an agent needs: trigger, scope, sibling routing, and exclusion of out-of-scope requests.

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 exactly one optional parameter (degreeType) with a full enum and 100% schema description coverage, so the schema already carries the semantics. The description never mentions the ability to filter by degree type, so it adds no meaning beyond the schema; baseline 3 applies.

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?

States a specific verb and resource ('list UET Taxila programs') and immediately scopes it to undergraduate offerings, with a concrete secondary use (comparing by closing merit / HSSC requirement). It explicitly distinguishes itself from get_uet_program and from other universities, so an agent can route correctly without opening the 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?

Explicit when-to-use ('user asks which undergraduate programs... or wants to compare by closing merit or HSSC requirement') and explicit when-not ('Do not use it for one program's details (use get_uet_program) or for other universities'). Both the positive trigger and the alternative are named.

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