search_in_pdf

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the basic action and fails to disclose important behavioral details such as whether the search works with scanned PDFs, what the return value looks like (e.g., page numbers, matches), or how edge cases (e.g., no match) are handled.

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, front-loaded sentence with no filler words. It effectively communicates the core purpose without redundancy, making it highly concise and well-structured.

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 tool has no output schema and no annotations, so the description should explain return behavior and limitations. It does not mention what the tool returns (e.g., page numbers, boolean, matches) or any constraints like text-based PDFs requirement. For a search tool, this is a significant gap when compared to sibling tools that have clearer outputs.

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?

The schema covers all three parameters with meaningful descriptions, so the baseline is 3. The tool description adds no additional parameter information, but since schema coverage is 100%, it does not need to compensate. The description is neutral on parameters.

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 clearly identifies the tool's function: searching for specific text within a PDF file. It uses a specific verb ('Search') and resource ('PDF file'), and distinguishes itself from siblings like 'read_pdf' and 'read_pages' which focus on reading rather than searching.

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 usage: use this tool when you need to find text within a PDF. However, it does not explicitly state when not to use it or how it compares to alternatives like 'read_pdf' or 'get_pdf_info'. There is no mention of exclusions or alternative selection.

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