Download folder as ZIP

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

Annotations declare readOnlyHint=false, idempotentHint=true, openWorldHint=true and destructiveHint=false, which already communicate safety and repeatability. The description adds only that the scope is the entire folder, but says nothing about where the ZIP is written locally, whether it requires authentication, size limits, or whether it overwrites existing files – notable gaps for a tool whose annotations mark it as a non-read-only, network-touching operation.

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 with no filler or repetition. It is efficient, though arguably under-specified rather than merely concise given the tool's complexity.

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?

With no output schema, no parameter documentation, and only partial annotation coverage, the description leaves too much unstated: where the archive lands, whether login is required, and how folderId maps to a library. For a download/write-to-disk tool, this is a significant shortfall.

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 0% and the description provides no parameter information at all. 'folderId' is inferable from the name, but 'outputDirectory' is ambiguous (optional destination path? server-side path? default behavior?) and is left entirely unexplained in both schema and description.

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 gives a specific verb ('Download'), a clear resource ('a whole Library folder'), and the output form ('as one ZIP file'), so the agent knows exactly what the tool produces. However, it does not differentiate itself from nearby siblings such as axcel_download_job or the other axcel_folder_* operations, so the agent must infer which one to pick.

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?

There is no statement of when to use this versus alternatives like axcel_download_job, nor any prerequisite such as being logged in. The only implied guidance is the word 'whole folder', which hints at bulk retrieval but does not name an alternative or a triggering condition.

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