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

Annotations already declare readOnlyHint=true, so safety is documented. The description adds that it returns matches with positions, which is useful but not critical. It does not disclose any other behavioral traits like permission requirements, rate limits, or handling of large files. Given the high annotation coverage, the description provides adequate additional context for this dimension.

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 sentence that is concise and to the point. Every word serves a purpose: it names the action, target, and result. There is no extraneous information, making it easy to parse.

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?

Despite having 6 parameters and no output schema, the description does not explain the structure of the returned matches (e.g., page numbers, coordinates, text snippets). It only vaguely mentions 'positions'. For a search tool, this is a significant gap that could lead to incorrect expectation of the output format.

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% with detailed parameter descriptions. The tool description does not add any further meaning beyond what the schema already provides. For example, it does not explain how 'regex' interacts with 'case' or the format of 'webhook_url'. Baseline 3 is 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?

The description clearly states the verb 'Search' and the resource 'PDF file', and specifies the outcome 'return the matches with their positions.' It distinguishes from siblings like 'search-pdf-content-with-ocr' and 'read-pdf-content' by not mentioning OCR and focusing on search rather than extraction.

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 provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, contexts, or when not to use it. The sibling list includes many PDF-related tools, but the description offers no comparison or exclusion criteria.

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