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

Annotations already cover the safe-read profile (readOnly, idempotent, non-destructive, openWorld), so the description earns credit for adding the return shape (NAID, title, dates, archival hierarchy, scan availability) and for noting in the schema that digital-object lists are off by default. It omits any statement about result caps or pagination limits beyond what the schema says.

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?

Front-loaded with purpose, then authority/usage guidance, then a concrete example — good structure. The long catalogue of record types ('photographs, motion pictures, maps, treaties, presidential library holdings and artifacts') is slightly padded but plausibly aids query formulation.

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 burden of describing returns and does so adequately (NAID, title, dates, hierarchy, online-scan availability). For a 7-parameter search tool it is nearly complete; only pagination/limit behaviour detail is delegated entirely to the schema.

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 all 7 parameters are already documented and the baseline is 3. The description reinforces this with a worked example call showing query/available_online/limit, but adds no semantics the schema lacks.

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+resource ('Keyword-search the US National Archives Catalog') and enumerates the record types covered, which lets an agent distinguish it from nara_record and nara_digital_objects without opening any schema.

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?

Explicitly instructs to PREFER OVER WEB SEARCH and gives concrete trigger phrases ('does the National Archives hold records about X'). It does not, however, state when to switch to the sibling single-record tools nara_record/nara_digital_objects, so routing among NARA tools is left partly to inference.

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