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

With readOnlyHint=true the safety profile is already covered, and the description still adds substantial behavior: conditional emission of version_count/source_count/first_edition_seen/last_edition_seen, source attribution rules, and the 'last seen in an older edition' case. No output schema exists, so this return-shape disclosure is doing real work, though it omits pagination/limit semantics beyond the schema.

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?

Purpose is front-loaded, but the prose is dense and some sentences are hard to parse ('reads exactly as it always has', 'the Union keeps a record no current catalog prints'). Most sentences carry information, yet the wording is more convoluted than needed for the content delivered.

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 must convey return structure, and it does so in detail for the conditional fields and source attribution. For a 3-param, zero-required list tool the coverage is close to complete, missing only explicit pagination guidance.

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 the schema already documents limit, query and offset. The description only loosely restates the query ('optional name or jurisdiction words') and adds nothing about limit or offset semantics, so baseline 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 opening question states a specific resource (statewide/compact transfer frameworks) and the filtering inputs, and the later sentence 'come from the one-record get, never from a list' implicitly differentiates it from get_transfer_framework. It is clear but the phrasing is oblique rather than a crisp verb+resource statement.

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 (search/list with optional filters; returns 'none held' when empty) and the one-record alternative is named for retrieving forms. There is no explicit statement of when to prefer this over find_agreements, find_pathways, or the other find_* siblings.

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