import_template

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

No annotations are provided, so the description carries the burden. It discloses that the return value is base64-encoded CSV with column headers and example rows, which is useful behavioral context. However, it doesn't mention the output size, whether it's a pure read operation (inherently implied by 'download'), or any format details beyond base64 encoding.

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 sentences, zero waste. Front-loaded with the core action (Download) followed by return format and downstream usage. Every clause earns its place.

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?

This is a simple 2-parameter, 1-required tool with 100% schema coverage. The description adequately covers the return format, the download nature, and the relationship to import_upload. Given its simplicity, the description is largely complete; it could optionally note that no auth headers or size limits apply, but for a tool this simple this is well-covered.

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 both parameters are already documented in the schema (importType with enum values, companyId as company UUID override). The description adds the clarification that companyId is an override when active company isn't set, but the schema already conveys this. The description's main added value is explaining what the returned template contains.

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 verb (Download) and resource (CSV template for a specific import type). It distinguishes this download/retrieval tool from the import execution siblings (import_execute, import_upload, import_preview) by making clear it just fetches a template.

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 states that the template is to be filled in and uploaded via import_upload, providing clear follow-up context linking to a sibling tool. It doesn't explicitly state when NOT to use it, but the coupling to import_upload gives adequate context.

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