pdf_search_batch

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

No annotations are provided, so the description must carry the behavioral burden. It does not disclose whether subdirectories are searched recursively, which regex flavor is supported, how matches are returned, or whether max_results truncates across files or pages, leaving key operational behavior unspecified.

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 single well-structured sentence with no redundant wording, and the core action and scope are front-loaded.

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?

The schema fully documents parameters, but the tool has no output schema and the description does not explain the return format or recursive-search behavior. For a five-parameter batch search tool, this leaves meaningful gaps despite the concise and clear core statement.

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 including defaults and meanings. The description adds only illustrative glob examples like '*.pdf' and 'L*.pdf', which is marginal value beyond the schema.

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 verb and resource: search across multiple PDF files in a directory, filtered by a filename pattern, for a keyword or regex. It implicitly distinguishes itself from single-file siblings like pdf_read_text by emphasizing batch search, but it does not explicitly name or differentiate from those alternatives.

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 batch-search scope implies when to use this tool, but there is no explicit guidance on when to choose it over pdf_read_text or pdf_get_metadata, nor any stated exclusions or prerequisites. The usage context is inferable rather than documented.

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