upload_to_file_store

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

Discloses that files are 'chunked and embedded by Google for retrieval', adding value beyond the openWorldHint annotation. No contradictory information.

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?

Three sentences, front-loaded main action, no redundancy or 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?

Covers purpose, supported formats, and processing. Output schema exists, so return values not needed. Could mention prerequisite store existence, but acceptable given context signals.

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 coverage is 100% with all parameters described. Description adds context on supported file formats but does not significantly enhance parameter understanding.

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 verb 'upload', resource 'FileSearch store', and purpose 'for semantic search'. Supported formats listed. Differentiates from siblings like 'upload_file' and 'create_file_store'.

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?

Implies usage context (uploading to a store for semantic search) and lists supported formats, but does not explicitly state when to use vs alternatives like 'upload_file' or exclude scenarios.

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