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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds real behavioral context beyond that: this tool returns a fully assembled aggregate (a 'whole' program with offerings campus-resolved and its institution), which tells the agent it does not need follow-up enrichment calls. It does not cover error/pagination behavior for the id lookup.

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?

It is a single, tightly packed sentence with the returned contents front-loaded and the chaining hint at the end. The fragment style ('One program whole:') is slightly informal but costs nothing in length, and no sentence is wasted.

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 compensates well by enumerating the returned entities, and with one required parameter at full schema coverage the input side needs nothing more. It stops short of describing nesting/shape of the returned aggregate, but is sufficient for an agent to decide to call it.

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 100%, and the schema already documents program_id with its source tools, so the baseline is 3. The description only adds the mild constraint that a single id is expected ('pass one'), without adding format or provenance detail 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?

The description names a specific verb+resource (get one program) and enumerates exactly what is returned: row, identifiers, offerings with campus resolved, institution, and award checklists. This clearly separates it from search/list siblings like find_programs and programs_for_institution, though it never names those siblings explicitly.

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?

Usage is implied rather than stated: 'pass one' signals a single lookup by id, and the trailing 'pass one to get_checklist' hints at a chaining workflow. However, there is no explicit when-to-use vs when-to-use-something-else guidance (e.g. get_program vs get_institution or vs the find_* tools).

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