pdf_search

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

Annotations already cover read-only, open-world, and idempotent behavior, and the description adds real value on top: it discloses the return shape, that hidden-text pages produce warnings, and an explicit prompt-injection caution that snippets are data, not instructions. It omits the 8 MiB fetch cap, but the schema carries that.

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 compact sentences, front-loaded with what is searched and where, followed by the return/warning semantics. No filler, no restated field names.

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 does the necessary work of explaining what comes back (file, page, snippet) and adds a hidden-text warning. Pagination/cap behavior is delegated to the schema, which is reasonable, so the only minor gap is anything about hit limits or result volume.

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 all seven parameters are already documented in the input schema; the description only restates the glob example and the 'exactly one of path/data/url' rule that the schema already states. Baseline 3 is appropriate since the schema 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?

States a specific verb and resource (search a PDF) and enumerates the three input modes (glob path, base64 data, https url), with the return being file/page/snippet. The purpose is unambiguous, though it never names pdf_text or pdf_info to mark the boundary between searching and extracting.

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 implies when the tool applies (finding text or a regex across one or many PDFs) and implies the three mutually exclusive input modes, but gives no explicit when-not guidance or comparison against siblings like pdf_text or pdf_info.

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