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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile needs no restating. The description's useful addition is that each returned entry carries a license and a refresh value. It says nothing about ordering, whether stale/inactive sources are included, or result size, which are the remaining behavioral unknowns for a list tool.

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?

One sentence, front-loaded with the verb and resource, with the payload contents appended where they help. No filler, no restatement of the tool name, nothing that could be cut without losing information.

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 parameters, no output schema, and full annotation coverage, the description is close to sufficient: it names the resource and the two fields an agent will get back. Minor gaps remain, such as ordering and whether every source is always returned, but a caller can invoke this correctly without further information.

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?

The tool takes no parameters and the schema is an empty object with additionalProperties=false, so there is no parameter meaning to explain. Baseline 4 applies; the description correctly implies the call is argument-free.

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 (list) and a precisely scoped resource: the provenance records behind the boarding school data, including license and refresh cadence. That distinguishes it from sibling list_* tools, which cover categories, places, and products rather than data sources. It stops short of any explicit sibling callout, but the resource is unambiguous.

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 only implied: an agent can infer this is the tool for provenance/licensing questions, but there is no statement of when to prefer it over alternatives or of any prerequisites. No exclusions or routing guidance are offered. Adequate for a zero-parameter lookup, but it leaves the when-to-use decision to inference.

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