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

Annotations only carry readOnlyHint=true, so the description carries most of the load and does it well: it discloses that the tool answers 'none held' for empty results, that source_url/capture_file/catalog_year/source_catalog_name belong to one form's source rather than the whole record, and that version_count/source_count/first_edition_seen/last_edition_seen appear only for multi-form/multi-source records. It does not cover pagination behavior or rate/limit implications, so it stops short of 5.

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 description is a dense, run-on block heavy with idiosyncratic jargon ('the Union', 'the build holds none', 'reads exactly as it always has') that is difficult to parse for an agent. It is front-loaded on the filters and empty-result behavior, but several clauses repeat the same conditional-field idea instead of stating it once economically.

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 explain return shape, and it does so in detail (row fields, conditional fields, source attribution, older-edition flagging), which is the correct burden for this tool. It omits any explanation of limit/offset paging beyond the schema's 'next_offset' hint, leaving a small gap.

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 all five parameters; the description only restates the three filter dimensions as 'title words, an agreement id, or a checklist id' without adding format or syntax insight. Baseline 3 applies when structured data does the heavy lifting.

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 states a specific resource ('Which pathways are held?') and its optional filters, and it implicitly distinguishes itself from the sibling get_pathway by declaring 'The forms themselves ... come from the one-record get, never from a list.' The verb is implied rather than named (it is a filtered list/find), which keeps it short of 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?

Usage is implied through the filter list and the routing note that per-form detail belongs to the one-record get, giving the agent a hint about when to reach for this tool versus get_pathway. There is no explicit when-to-use/when-not statement and no mention of the other find_* siblings (find_agreements, find_checklists) that overlap with the agreement_id/checklist_id filters.

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