Datasheet indir

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

Annotations declare a non-read-only, open-world, idempotent, non-destructive operation, and the description explains why it is idempotent (existing files are reused unless overwrite=true) and discloses the filesystem side effect and default location. It stops short of describing failure cases, such as products with no datasheet available or permission errors.

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?

Four short sentences, front-loaded with the purpose and return value, then the configuration default, then caching, then the sibling redirect. No redundant or filler wording.

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?

With no output schema, the description usefully states that a file path is returned, and it covers defaults and overwrite semantics for a 4-parameter tool. Error behavior for missing datasheets and the exact response shape are the only notable omissions.

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%, so the baseline is 3, but the description adds the default folder value (~/Downloads/ozdisan-datasheets) and the OZDISAN_DOWNLOAD_DIR environment override with its precedence, neither of which appears in the 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?

States a specific verb and resource ("Download a product's datasheet PDF to the local disk") plus the return value (file path). It also distinguishes itself from the sibling read_datasheet by naming it as the tool for reading content.

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?

Explicitly routes the agent: use this tool to save the PDF, use read_datasheet to read the content. Caching behavior (reuse unless overwrite=true) tells the agent it can call this repeatedly without side-effect concerns.

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