create-drive-item-preview

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

Beyond annotations (destructiveHint=true), the description adds that the URL is short-lived and returns getUrl and postUrl. It does not contradict annotations and provides useful behavioral details about the response.

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 relatively concise but could be better structure. The first sentence 'Invoke action preview' is vague; the tip is helpful but uses an emoji and informal formatting. Key information is present, but not optimally front-loaded.

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 complexity (nested body, no output schema) the description covers return values, use case, and body fields. It omits details about optional parameters (includeHeaders, excludeResponse) and authentication, but these are in the schema. Overall adequate for selection and invocation.

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?

The description explains the body parameters (page, zoom, viewer) with examples and types, adding meaning beyond the schema which only has generic path parameter descriptions. The schema covers 80% of parameters, but the description enhances understanding of the nested body object.

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 description clearly states the tool generates a short-lived embeddable preview URL for files, specifying supported types (Office docs, PDFs, images). It distinguishes itself from sibling tools like create-drive-item-share-link by focusing on preview rather than sharing.

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 description advises using the tool for inline previews in emails or chats, implying when it is appropriate. However, it does not explicitly state when not to use it or compare with alternative tools, leaving some ambiguity.

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