dotloop_download_document

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

Without annotations, the description provides minimal behavior info: it mentions a byte-size limit but does not explain what happens if exceeded (truncation? error?), nor any side effects, auth requirements, or rate limits.

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 very concise (one sentence, 9 words) and front-loaded. However, given the tool has 5 parameters and no parameter documentation, the description is under-specified; a bit more detail would be beneficial.

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 is minimally complete. It does not explain how to use optional parameters, error handling, or confirm if the output schema sufficiently describes return values. More context is needed for a tool with multiple parameters.

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 0% (no parameter descriptions), and the tool description adds no explanation of parameters like folder_id or max_bytes beyond their names. The names are somewhat self-explanatory, but lack of detail reduces usefulness.

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 Dotloop document, specifies the format as base64, and mentions a byte-size limit. This distinguishes it from sibling tools like dotloop_get_document (metadata) and dotloop_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?

No guidance on when to use this tool versus alternatives (e.g., dotloop_get_document) or when not to use it. Missing context about suitable scenarios or prerequisites.

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