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

Annotations already declare the safe read-only profile, so the description's real value is the return-format behavior it adds: Docs/Slides come back as text, images as viewable pictures, spreadsheets and PDFs unsupported. That is rich context beyond the annotations, though auth/rate-limit details are absent.

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?

Front-loaded with the core action, then file-type behaviors, then exclusions, then id sourcing. Every sentence carries distinct information and none is padding.

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 correctly explains what is returned for each file type and what is unsupported. It is nearly complete for a read tool; only edge cases like very large files or permission failures are unaddressed.

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 50%: the mailbox param is documented in-schema while itemId is not. The description compensates by telling the agent to get the id from list_gdrive_items or search_gdrive_items, giving useful sourcing semantics for the otherwise-undocumented parameter.

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 (read/open) and resource (one Drive file) and enumerates what different file types yield, which cleanly separates it from read_google_sheet_range and read_onedrive_file. An agent can identify the tool without opening the 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?

Explicitly states when NOT to use it (spreadsheets are refused in favour of read_google_sheet_range, PDFs cannot be read yet) and names the alternative tool. It also tells the agent where to obtain the required id, covering the full invocation path.

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