get_attachment

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

The description details the return fields (base64 bytes, filename, mime_type, size_bytes, data_text) and the max_size_bytes cap, sufficiently describing the read-only behavior without 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?

Two sentences cover purpose, prerequisites, return format, and size cap without any redundancy.

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 core functionality and key constraints, but lacks details on error handling or edge cases like missing attachments.

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 adds context for message_id and attachment_id by linking to list_thread_attachments, supplementing the 50% schema coverage. However, it does not elaborate on the account parameter 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?

The description explicitly states the tool fetches a Gmail attachment using message_id and attachment_id, and distinguishes from siblings by referencing list_thread_attachments for discovery.

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 clearly implies the prerequisite of using list_thread_attachments to obtain the IDs, but does not explicitly state when not to use or list alternatives.

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