Download document file

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

Beyond annotations (readOnly, idempotent, etc.), the description adds key behavioral details: it returns the saved file path and size, and states that file content is NOT loaded into the conversation, making it safe for large PDFs. This complements the annotations and provides valuable context for the agent.

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 three sentences, front-loaded with the main purpose, and clearly structured. Each sentence earns its place: purpose, formats, and return/safety note. No wasted words.

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 no output schema, the description explains return values (path and size). It covers formats, safety, and behavior. Missing is what happens if the file already exists (overwrite?) or if the directory doesn't exist (schema says parent must exist, but description doesn't mention it in context). Still, it is largely complete for a moderate-complexity tool with good annotations.

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. The description adds meaning to the 'format' enum by explaining what each format is (e.g., 'PDF with embedded XML', 'first page as an image'), which goes beyond the bare schema descriptions. It also clarifies the purpose of output_path in context.

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 a document file to a local path, with specific verb ('Download') and resource ('document'). It lists supported formats and distinguishes from the sibling tool 'easybill_download_attachment' by focusing on documents rather than attachments.

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 implies usage (e.g., when you need a PDF or e-invoicing file saved locally) and explains return behavior, but it does not explicitly mention when to use this over alternatives like 'easybill_download_attachment' or provide exclusion criteria. Context is present but no clear when-not-to-use guidance.

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