alefba_download_pdf

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

Explains parameter effects (quality, color, img_format) and return behavior (download info vs. saved path). Lacks details on whether the operation is synchronous, modifies state, or requires prior analysis.

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 front-loaded with English purpose but includes redundant Persian translation. Could be more concise without losing clarity.

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?

Adequate for a 6-param tool with output schema; explains all parameters except document_url. Missing contextual info like document must exist and be analyzed, and any limitations or prerequisites.

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 has 0% description coverage, so description compensates by explaining quality (0-100), color (color vs grayscale), img_format (png|jpg), save_path, and instance. Adds meaning beyond schema names.

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 downloads the analyzed document as a searchable PDF, with a distinct verb and resource. It differentiates from sibling tools like download_excel and download_original.

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?

No guidance on when to use this tool versus alternatives (e.g., download_original, download_word). Missing prerequisites like document must be analyzed first.

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