Get a Drive file’s details

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so 'Read-only' largely restates structured data. The description does add useful disclosure of what metadata comes back (webViewLink to open, webContentLink to download), which is beyond the annotations, but no auth or rate-limit context.

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 sentences, front-loaded with the primary action and the enumerated return fields, then the parameter hint and safety note. No filler; every clause carries information.

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?

With no output schema, the description usefully enumerates the key return fields, covering what the agent needs to know before calling. Minor gaps remain around error behavior for invalid or inaccessible file ids, but the core need is met.

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 100%, with fileId fully documented, so the baseline is 3. The description only repeats the origin of the id ('from list_drive_files') without adding format or constraint detail beyond the schema.

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?

States a specific verb (Fetch) and resource (one Drive file's metadata) and enumerates the returned fields, distinguishing it from list_drive_files, update_drive_file, and the OneDrive equivalents. An agent can identify the tool without opening either schema.

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?

Clearly indicates the context (pass fileId, sourced from list_drive_files), which routes the agent from the list tool to this one. It lacks explicit when-not guidance or exclusion relative to e.g. get_onedrive_file, so it falls short of a 5.

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