Workbooks Export And Download

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

Annotations declare a non-read-only, open-world, non-destructive operation, and the description usefully adds behavior beyond that: it polls until ready (async lifecycle), truncates to size-info when max_bytes is exceeded, and returns base64-encoded content on success. The timeout_seconds parameter is undocumented behaviorally, which keeps it short of a 5.

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?

Front-loads the core action in one sentence, then adds compact per-parameter notes with no filler. Every line carries information an agent needs; nothing is redundant with the schema.

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?

An output schema exists, so return values need not be fully explained, and the description still notes the base64 payload shape. Combined with the format/layout/parameters/max_bytes coverage, an agent has enough to call it correctly; only timeout_seconds and element_id semantics are left entirely to the bare schema.

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%, so the description must carry the burden and largely does: it enumerates the format values (csv/pdf/xlsx/png), restricts layout to pdf, gives a concrete parameters override example, and explains max_bytes default and overflow behavior. It omits element_id and timeout_seconds, so it does not fully compensate for the 7-param, 0%-coverage schema.

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?

States a specific verb+resource: 'Export a workbook/element and download the result.' An agent can tell this is a produce-and-fetch tool. However, it never differentiates itself from the very close siblings 'workbooks_export_workbook' and 'workbooks_download_query_export', which an agent could easily confuse it with.

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 gives no when-to-use vs. when-not guidance and never names an alternative. 'Polls until ready' implies a long-running/blocking operation, which is mild usage context, but nothing tells the agent why to pick this over workbooks_export_workbook or workbooks_download_query_export.

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