pdf_discovery

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

No annotations are provided, so the description must convey behavioral traits. It implies read-only, non-destructive behavior ('discover', 'search and listing'), and hints at performance ('fast'). However, it lacks details on side effects, rate limits, or what 'without full processing' means in practice.

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 efficiently conveys the core purpose. It is front-loaded and contains no extraneous information, though it could benefit from slight restructuring to separate purpose from behavior.

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?

Given the tool's 4 parameters, no output schema, and many sibling tools, the description is too sparse. It does not explain the return format, pagination, or limitations, leaving the agent with incomplete context for effective usage.

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?

All 4 parameters have schema descriptions covering 100% of properties, so the baseline is 3. The description adds 'fast search and listing' but does not enhance parameter understanding beyond what the schema provides.

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 tool's purpose: 'Discover PDF documents without full processing - fast PDF search and listing.' It uses a specific verb ('discover') and resource ('PDF documents'), and distinguishes from sibling tools like analyze_pdf by mentioning 'without full processing.' However, 'without full processing' is somewhat ambiguous.

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. There are many sibling search tools (e.g., search_arxiv, search_pubmed) but no comparison or contextual hints, leaving the AI agent to infer usage without explicit direction.

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