vnt_google_docs_fetch

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 core read/download action and output format, but does not disclose whether local files are overwritten, what authentication is required, or whether any side effects occur. This is insufficient for a tool that creates local files.

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 sentence that is front-loaded with the action and resource. It is concise and free of filler, achieving maximum clarity with minimal text.

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 7 parameters, no annotations, and no output schema, this sparse description is incomplete. It lacks details about authentication, multi-sheet handling, file naming, and error cases. The schema covers some output naming rules, but the description does not provide enough context for reliable invocation.

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 only 43%, and the description does not compensate. It adds no meaning about parameters beyond the schema's existing descriptions. For instance, spreadsheet_id, api_key, service_account, and sheet_names remain undocumented 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 uses a specific verb ('Fetch') and resource ('Google Spreadsheet') with a clear output format ('local CSV/TSV'). It distinguishes itself from sibling tools like vnt_google_docs_list_sheets (which lists sheet names) and vnt_google_docs_line_stats (which provides stats) by indicating this tool downloads spreadsheet data to local files.

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 phrase 'for google_docs extract/insert' implies the tool is a preparatory step for subsequent extract/insert operations, giving some sense of when to use it. However, it does not explicitly state when to prefer this tool over alternatives, nor does it mention exclusions or prerequisite steps.

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