create-drive-item-preview

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

Annotations indicate destructiveHint=true, suggesting side effects, but the description describes only generating a URL (non-destructive) and does not clarify what is destroyed or why the hint is set. It adds information about return URLs but fails to reconcile with the annotation.

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 short but not well-structured; it starts with a vague sentence and then a tip. It front-loads the verb 'Invoke' instead of the resource. Every sentence adds some value, but the structure could be improved.

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?

The description covers the basic purpose, use case, and key parameters/return values. However, it does not explain the destructiveHint annotation, nor does it fully describe all parameter options (e.g., viewer values). The lack of output schema is partially compensated by listing return fields.

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 80%, so baseline is 3. The description adds value by listing body parameters (page, zoom, viewer) and explaining return fields (getUrl, postUrl). However, it does not detail viewer enum values or other parameters beyond what the schema provides.

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 initial sentence 'Invoke action preview' is vague, but the tip clarifies that the tool generates a short-lived embeddable preview URL for files. Among siblings, it is the only tool for creating previews, so its purpose is distinct.

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 tip provides a use case ('useful for surfacing inline previews in summary emails or chat messages'), but does not explicitly state when to use or avoid this tool compared to alternatives (e.g., get-drive-item). No exclusion criteria or alternative tools are mentioned.

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