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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is covered. The description adds the returned fields, but those are also available via the output schema, and it says nothing about result ordering or how multiple filters combine. It adds modest value beyond structured fields.

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?

Two short sentences, front-loaded with the core purpose, and the second sentence carries a genuinely useful cross-tool handoff. No filler.

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 an output schema, complete annotations, and fully documented parameters, the description only needs to supply purpose and routing — both present. The minor gap is not explaining how name/state/city filters combine, but nothing essential to a correct call is missing.

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% and all five parameters (city, name, state, page, per_page) are documented with examples and bounds in the schema. The description names the same three filter dimensions but adds no syntax or combination semantics beyond the schema, 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?

States a specific verb and resource ('Find newspapers in the archive') plus the three filter dimensions (name, state, city). It also implicitly distinguishes itself from search_newspapers by positioning itself as the metadata lookup that yields the LCCN needed for content search.

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?

The description explicitly routes the agent onward: the returned LCCN is to be used as newspaper_lccn in search_newspapers to narrow to a single paper. That is clear workflow context, though it does not state exclusions (e.g. when to skip this step and search directly).

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

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is covered by structured data. The description adds that results carry the page's opening text (usually top headlines) and a page_url, which is modest added value; it says nothing about result caps, pagination totals, or ordering that isn't already in 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?

Two short sentences with zero waste. The core action is front-loaded in the first sentence, and the second sentence covers result content plus the downstream handoff, all of which earns its place.

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?

An output schema exists, so return values need not be explained in detail, and annotations cover the safety profile. The description covers purpose, a use case, and the follow-up tool; only minor gaps remain (no mention of pagination limits or how state filtering interacts with results).

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% (date format, state, page, per_page all documented in the schema), so the schema carries parameter meaning. The description adds no format hints, defaults, or semantics beyond it, 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 verb and resource ('List newspaper front pages published on a specific day'), which is unambiguous and clearly distinct from search_newspapers and find_newspapers. It does not explicitly contrast itself with those siblings, but the mention of get_page_text as a downstream step gives the agent routing context.

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?

Gives a concrete usage scenario: '"what was the news on <date>" questions.' This tells the agent when the tool is appropriate. It stops short of naming an alternative or an exclusion (e.g., when to prefer search_newspapers instead), so it is clear context without full routing guidance.

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

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

Annotations already cover the safety profile (readOnly, idempotent, openWorld), so the description's added value is the chunking behavior: long pages come back in chunks and a `truncated` flag signals when to re-call. That is a real behavioral trait not derivable from annotations or 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?

Two short sentences, front-loaded with the core capability and followed by the pagination caveat. No filler and nothing that fails to earn its place.

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?

An output schema exists, so return values need not be explained, and the description still adds the one thing an agent must know to drive it correctly: how to continue after a truncated response. Nothing essential is missing.

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 coverage is 100%, so the baseline is 3. The description goes slightly beyond the schema by tying `offset` to the truncation flow (`truncated` true -> re-call with `next_offset`), giving the parameter a purpose the schema field alone does not convey.

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 and resource ('Read the full OCR text of one newspaper page') plus what comes with it (citation, scan/PDF links). It is clearly distinguishable from the sibling search tools by being a retrieval operation, but it does not explicitly name any sibling to route against.

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 gives clear continuation guidance for the truncated case ('call again with offset set to next_offset'), which is genuine usage instruction. However, it never says when to reach for this tool versus search_newspapers or front_pages_on_date, so tool-selection guidance is only implied.

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

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

Annotations already declare readOnly, openWorld and idempotent, so safety is covered. The description adds real behavioral context beyond that: broad searches are slow (performance/latency warning) and the result shape includes a page_url intended for get_page_text chaining.

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?

Two short paragraphs, front-loaded with what the tool does and followed by the result shape and the efficiency caveat. No sentence is filler.

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 an output schema present, the description need not explain return fields, yet it still summarizes them usefully. Parameters are fully documented in the schema. Minor gaps remain (page/per_page limits, no explicit next-step for pagination), but nothing needed to invoke the tool is missing.

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 baseline is 3. The description goes slightly beyond it by recommending which filters (date range, state/newspaper) actually make searches fast, giving practical meaning to start_date, end_date, state and newspaper_lccn rather than restating them.

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 (Search) plus resource (full text of historical US newspaper pages) and even bounds the corpus (1700s-1963). It hints at the workflow handoff to get_page_text, but never contrasts itself with find_newspapers or front_pages_on_date, so sibling differentiation is only partial.

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?

'Add a date range and a state or newspaper whenever possible; broad searches are slow' gives clear when-to-narrow guidance and a performance rationale. It stops short of explicit exclusions or naming when a sibling (e.g. find_newspapers to resolve an LCCN) should be used instead.

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