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

Annotations already declare readOnlyHint=true, so the read-only safety profile is covered structurally. The description adds useful domain semantics about what a checklist represents but says nothing about result volume, ordering, or how pagination behaves in practice, so it adds only modest behavioral context.

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 primary question is front-loaded in the first sentence and the filtering guidance follows immediately. It is compact and wastes little, though the em-dash apposition makes the opening sentence slightly heavier than it needs to be.

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 read-only list tool with a fully documented 5-param schema and no output schema, the description supplies the essential domain framing and sibling routing. Missing are expectations about result shape and pagination flow, which are largely implied by the schema's offset/limit fields.

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%, so limit, offset, unitid, query and program_id are all documented in the schema. The description confirms that query/program_id act as narrowing filters but adds no syntax, format, or interaction detail beyond that, making the baseline 3 appropriate.

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 resource (checklists published by an institution) and even defines the domain term — 'the generic itinerary of requirements for an award' — which removes ambiguity an agent could not resolve from the name alone. It is clearly distinct from the singular sibling get_checklist.

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 explains that award words or a program id narrow the result set and explicitly routes to get_checklist when one checklist is wanted. It does not state when this tool should not be used (e.g. versus compare_program_checklists or checklists_requiring_learning_unit), so it falls short of full routing guidance.

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