download_pdf

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

No annotations provided, but description discloses search behavior (fuzzy vs exact match), download source (MinIO), and output details (local directory). Return value is documented. Adequate for a file download tool.

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?

Description is moderately concise with a structured docstring format (Args, Returns). It could be slightly more direct, but it's well-organized and free of fluff.

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 complexity (download from MinIO, fuzzy matching), no annotations, and presence of output schema, the description is complete. It covers purpose, parameters, behavior, and return values.

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?

With 0% schema description coverage, the description fully compensates by explaining each parameter: title (fuzzy match), output_dir (default), exact_match (boolean). Adds meaning beyond the bare 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?

Description clearly states the tool downloads PDF files from a database based on title, using specific verbs and resources. It distinguishes from siblings like import_pdf (upload) and get_document (metadata retrieval).

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?

Description implies usage when needing to download a PDF by title, but lacks explicit guidance on when not to use or comparison to alternatives like search tools. Context from sibling names provides some differentiation.

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