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 profile is fully covered elsewhere. The description adds the data scope and the 2022-2024 temporal range of the merit history, which is useful, but says nothing about caching, response shape, or failure behavior when the slug is absent.

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, zero filler. The positive scope and the returned fields come first, and the exclusion clause follows immediately after, making it easy to scan.

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?

For a single-parameter, output-schema-backed, read-only lookup tool, the description supplies everything needed: what is fetched, which fields come back, the date range covered, and which requests belong to sibling tools. Nothing required for correct invocation is missing.

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 an enum with a slug example, so the schema carries the parameter documentation. The description only reinforces that exactly one program is fetched, adding no format or validation detail beyond what the schema provides — 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 ('get') and resource ('one UET Taxila undergraduate program') and enumerates the returned fields (credit hours, duration, accreditation body, minimum HSSC percentage, closing merit history). It explicitly distinguishes itself from list_uet_programs ('Do not use it for listing all programs'), so an agent can route correctly without opening schemas.

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?

Gives explicit when-to-use ('a user asks about one ... program') and when-not ('Do not use it for listing all programs or for programs at other universities'). The single-result scope constraint effectively selects this tool over list_uet_programs and the other siblings.

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