Get a Drive file’s details

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

Annotations already declare readOnlyHint=true and openWorldHint=true; description adds value by detailing returned fields (webViewLink, webContentLink) and confirming read-only behavior. No contradictions.

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 front-load the purpose and key details. Every word is informative; no fluff.

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 presence of an output schema (not shown but noted), the description sufficiently covers what the tool does and returns. It is complete for a simple get-by-ID operation.

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 for fileId is already 100% covered and matches the tool description ('the Drive file id (from list_drive_files)'). Description adds no new semantics beyond the schema, so baseline 3.

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 'Fetch one Drive file's metadata' and enumerates specific fields returned (name, type, size, modified time, webViewLink, webContentLink). Distinguishes from siblings like list_drive_files (list all) or update_drive_file (modify).

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 instructs to 'Pass fileId (from list_drive_files)', providing prerequisite guidance. Also notes 'Read-only' to indicate no side effects. Lacks explicit when-not-to-use or alternatives, but given the simple nature, it's adequate.

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