Download File from Kintone

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

With no annotations provided, the description discloses the tool's behavior: downloads, saves locally, returns path. It also details required conditions and permissions, implying it is read-only. Missing are specifics on potential errors (e.g., invalid fileKey, missing directory) but overall transparent.

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?

Two concise sentences: first defines action, second states requirements. No unnecessary words or redundancy. Front-loaded with the core purpose.

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?

The description covers the return value (absolute path), prerequisites, and output schema existence is noted. Minor gap: no mention of error handling or edge cases, but sufficient for typical use.

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% and each parameter has a clear description. The tool description adds no new semantic information beyond the schema, which already explains fileKey and fileName extensions. Baseline 3 is appropriate.

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 using its fileKey and saves it to a configured directory, returning the absolute path. This distinguishes it from sibling tools which focus on CRUD operations on records and forms, none of which handle file downloading.

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 specifies prerequisites (KINTONE_ATTACHMENTS_DIR env var, viewing permissions) which guide usage. While no explicit alternatives or when-not-to-use are given, the tool's unique function among siblings implicitly indicates appropriate usage.

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