tealfabric_download_document

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It usefully reveals that file content is base64-encoded for binary-safe transfer, which is meaningful behavior beyond the schema. It does not mention auth, errors, or size limits, but for a read-only download the most important behavior is captured.

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?

A single front-loaded sentence states the operation and the critical return format. There is no filler or redundancy.

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 tool is simple, the schema fully documents both parameters, and the description supplies the return-format detail that would otherwise be missing given the absence of an output schema. Minor gaps like error behavior or tenant default handling are not critical for a basic download operation.

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 100%, so the baseline is 3. The description does not add further meaning to file_path or tenant_id beyond what the input schema already provides.

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 uses a specific verb ('Download') and names the resource ('document/file from Tealfabric documents storage'), and it adds the key detail that the file content is returned as base64. This clearly distinguishes the tool from siblings like get_document_metadata or list_documents.

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 imperative 'Download' makes the intended use obvious, and mentioning base64 output helps an agent choose this tool when raw file content is needed. It does not explicitly name alternatives or exclusions, but the context is clear enough for a straightforward retrieval tool.

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