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

Beyond the readOnlyHint annotation, it discloses meaningful conditional behavior: version_count, source_count, first_edition_seen and last_edition_seen appear only when a record has more than one form or source, and a record with one form/source omits them. It also notes older-edition retention via the Union. Return-shape behavior is described without an output schema, adding real value.

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 main purpose is front-loaded, which is good, but the prose is dense and cryptic, with run-on sentences and awkward phrasing ('a record with one form and one source carries none of them and reads exactly as it always has'). Several clauses are hard to parse on first read.

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 explaining the return shape and does so, including conditional fields and provenance semantics (source_url, capture_file, catalog_year belong to one form's source, not the whole record). It is adequate, though the obtuse style leaves some room for misinterpretation.

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 program_id parameter is fully documented in-schema (with an example and a pointer to programs_for_institution / find_programs). The description adds nothing about the parameter, so the baseline of 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?

The description names a specific verb+resource ('One program whole') and enumerates what it returns: its row, identifiers, offerings, institution, and checklists. It also distinguishes itself from list siblings ('The forms themselves... come from the one-record get, never from a list'). The dense phrasing muddies an otherwise clear scope.

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?

It implies a routing relationship ('pass one to get_checklist') and states that full form content comes from the single-record get rather than a list. However, it never explicitly says when to choose this over find_programs or programs_for_institution, so context is only inferable.

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