get-drive-item

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds valuable behavioral context: it explains the tool is read-only and nullable, lists exact fields returned (name, size, etc.), and warns about the potentially enormous payload of fetchAllPages. There is no contradiction with annotations.

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 somewhat verbose with a list of fields and a tip. The opening sentence is misleading ('All items') and could be simplified. While it packs useful information, it could be more concise and front-loaded accurately.

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?

Despite lacking an output schema, the description thoroughly explains what the tool returns (a list of metadata fields) and covers important context like pagination, download alternatives, and the nullable nature. It provides enough information for an agent to use the tool correctly.

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 good descriptions for all 7 parameters. The description adds extra context beyond the schema, particularly for the 'select' and 'expand' parameters, and provides a warning for 'fetchAllPages' about payload size. This adds value beyond the schema baseline.

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 it 'Gets metadata for a file or folder', which identifies the verb and resource. However, the opening line 'All items contained in the drive' is misleading, as the tool retrieves a single item, not all items. It distinguishes from siblings like get-download-url and download-bytes by explaining when to use those alternatives.

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 explicitly provides usage guidance: it tells when to use this tool for metadata, and when to use alternatives (get-download-url for large files, download-bytes for small files). It also warns against using fetchAllPages unless necessary, offering best practice advice.

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