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

With only readOnlyHint=true in annotations, the description adds real behavioral context: 'Nothing is summed or computed by the service,' 'Schedule is stated not held,' and that absent institutions/checklists/costs are explicitly stated as missing rather than omitted. These clarify gap handling beyond the annotation, though return format and paging semantics are only implied.

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?

Dense but purposeful — the comparison target is front-loaded, then the work-effort/cost distinction, then the no-computation and gap-statement guarantees. Mildly run-on phrasing costs it a point rather than any wasted sentence.

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 return-shape burden and does so: requirement groups, items, credit strings, and the tuition/fee policy are enumerated. It is usable as-is, though a concrete note on how the paired cost and checklist are keyed would make it fully self-contained.

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%, so unitids, program, detail, and institution_offset are already documented, including the 5-per-call batching. The description reinforces the per-UNITID semantics but adds no syntax or format detail beyond what the schema provides, so the baseline 3 holds.

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 (compare) and resource (a program's published checklists across several institutions), plus the paired cost dimension, so the agent can tell it apart from single-record siblings like get_checklist or find_checklists. It stops short of naming a sibling explicitly, which is what would push this to a 5.

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 multi-institution framing implies the use case (comparing one program across UNITIDs) but no sentence states when to prefer this over find_checklists/get_checklist or what to do when a single institution is wanted. Usage is left to inference.

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