fetch_job_file

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

With no annotations, the description must disclose behavioral traits. It mentions resumability, bounded max file size, and that bytes are written to disk (not inline). However, it lacks details on authentication, failure modes, or the exact max file size. The security aspect of allow_outside_cwd is mentioned only in the schema, not the description.

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 action, and no redundancy. It could be slightly more compact but is efficient overall.

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 7 parameters, no output schema, and no annotations, the description is incomplete. It misses parameter details, return value information (e.g., success/failure indicators), and error scenarios. Basic operation is covered, but depth is lacking for a complex file download tool.

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 43% (3 of 7 parameters have descriptions). The general description does not explain individual parameters beyond what the schema provides. The description adds context about file result usage but does not cover the undocumented parameters (kind_offset, timeout_secs, provider_npub).

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 file result to a local path, specifies the prerequisite (after submit_and_pay_job or get_job_result reports a file result), and distinguishes it from siblings that handle job submission or status. The verb 'download' and resource 'job result FILE' are precise.

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 explicitly says 'Use this after submit_and_pay_job or get_job_result reports a file result', providing clear context for when to use. It does not explicitly state when not to use or name alternatives, but the context is sufficient.

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