Скачивание чека в файл

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

The description significantly enhances the annotations: it discloses the default save location, states that existing files are not overwritten, explains that overwrite=True is required to replace a file, and reveals the 0600 permission behavior. These side effects are not visible in the annotations or schema.

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 compact and well organized: action first, then file behavior, then parameter source guidance. Every sentence carries essential operational information; there is no filler.

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?

For a 3-parameter tool with an output schema, the description covers default behavior, path customization, overwrite semantics, file permissions, and valid payment_id provenance. Nothing needed to invoke it correctly is missing.

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 description coverage is 0%, so the description must compensate, and it does: save_to is explained as a custom file path, overwrite is explained with its default behavior, and payment_id is precisely grounded in specific response fields and methods. The agent can reliably populate all three parameters.

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 first sentence states a specific, concrete action: download a PDF receipt for a payment. The object and format are clear, and the tool is effectively distinguished from broader siblings such as documents or ticket files.

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 gives explicit guidance on where payment_id can and cannot be obtained, naming the five valid sources and explicitly excluding list_operations. This is strong when-to-use and when-not-to-use instruction that prevents a common agent error.

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