download_google_doc_images

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action ('download') but doesn't cover permissions needed, rate limits, file formats supported, error handling, or whether it overwrites existing files. For a tool that likely involves file system operations and API calls, this leaves significant gaps in understanding its behavior.

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 a single, efficient sentence that front-loads the core action and resource. It wastes no words and is appropriately sized for the tool's complexity, making it easy to parse quickly.

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?

Given the tool has an output schema (which likely covers return values), the description's job is reduced. However, with no annotations, 3 parameters (one undocumented due to 0% schema coverage), and operations involving downloads and file system changes, the description is incomplete. It should address more behavioral aspects like error cases or output specifics beyond what the output schema might provide.

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 compensate for undocumented parameters. It mentions 'document_id_or_url' and 'output_dir' implicitly but doesn't explain what 'tab_id' does or provide details on parameter formats (e.g., URL patterns, directory paths). The description adds minimal value beyond the schema's property names, failing to fully address the coverage gap.

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 action ('download') and resource ('image objects from a Google Doc'), specifying the destination ('to a local folder'). It distinguishes from siblings like 'read_google_doc' or 'inspect_sheet_images' by focusing on downloading images rather than reading content or inspecting images in sheets. However, it doesn't explicitly differentiate from all siblings, such as 'export_google_file', which might handle similar operations.

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 provides no guidance on when to use this tool versus alternatives like 'export_google_file' or 'inspect_sheet_images'. It lacks context on prerequisites (e.g., authentication), exclusions (e.g., not for text extraction), or specific scenarios (e.g., batch image extraction). Usage is implied by the action but not explicitly defined.

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