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

Annotations already declare readOnlyHint=true and openWorldHint=false; the description restates "Read-only" and, more usefully, discloses the shape of the returned data (weeks, dates, pay-in-full/deposit prices, enrollment-open flag, prefillable questions with kind/choices/required, who fills it, outstanding tasks) despite there being no output schema. It does not cover failure modes (e.g. unknown or inactive program) or caching/freshness.

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?

The payload is front-loaded in a single dense sentence, followed by a compact program legend that is genuinely necessary. The main sentence is long and list-heavy, but no clause is redundant with structured fields except the brief "Read-only" restatement.

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 only one parameter, no output schema, and read-only annotations, the description supplies everything an agent needs: the return payload's contents, the program legend, and the interview-preparation context. Nothing material is missing for a tool of this complexity.

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 description coverage is 0%, so the description carries the burden, and it does so completely: every enum value is glossed with its real-world meaning (sonata = adult week-long camps, intermezzo = adult long weekends, capriccio = Capriccios & Suites, sonatina = children's Summer Sonatina, virtual = online courses). This adds genuine semantic value beyond the bare enum list.

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 names a specific verb (get) and resource (one program's enrollment form) and enumerates exactly what the payload contains: upcoming weeks with prices and open/closed status, prefills for questions, who must fill it in, and remaining tasks. This is clearly distinguishable from get_catalog (programs/courses) and build_enrollment_link (link creation).

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 framing "Everything needed to interview someone for one program's enrollment form" implies the use case (prepping an enrollment interview), but there is no explicit when-to-use, when-not, or named alternative such as build_enrollment_link for actually creating a link. The agent must infer the boundary from the purpose alone.

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