drive_files_export

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

Read-only nature is consistent with readOnlyHint annotation. Description adds that return is JSON metadata, which is useful context beyond annotations. No mention of permissions or rate limits, but sufficient given annotations.

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?

Two concise sentences: first defines action and scope, second provides sibling guidance and return type. No wasted words.

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?

For a simple export tool with two parameters, the description covers purpose, supported files, return format, and alternative usage. No output schema, but return type is mentioned. Complete given complexity and context from siblings.

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?

Input schema already provides descriptions for both parameters (fileId and mimeType) with mimeType listing possible formats. The description does not add new parameter insights beyond what schema provides, so baseline 3 applies due to 100% schema coverage.

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?

Clearly states the tool exports a Google Workspace file to a specific format, specifying file types (Doc, Sheet, Slide) and return type (JSON metadata). Distinguishes from sibling tool drive_files_download.

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?

Explicitly directs to use drive_files_download for automatic export with inline content, providing clear alternative for when the agent wants content instead of metadata.

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