Download Chat Attachment

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

Annotations (readOnlyHint=false) indicate potential side effects, and the description adds context: 'saves to local disk' (modifying local state) and mode-dependent return behavior (file path vs. temporary URL). This goes beyond annotation information.

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 exceptionally concise (two sentences) and well-structured: first sentence defines purpose, second explains mode differences. Every sentence adds value with no 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 explains return behavior for both modes but omits essential context: how to obtain 'user_google_email', error handling, size limits, or prerequisites. Given the tool has an output schema, return format is covered, but other aspects are missing.

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 67%, but the tool description does not add any parameter-level details. The 'user_google_email' parameter lacks schema or description explanation, leaving the agent to infer its purpose. No additional semantics are provided.

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 verb ('Downloads'), resource ('attachment from a Google Chat message'), and outcome ('saves to local disk'). It effectively distinguishes this tool from siblings like 'get_gmail_attachment_content' or 'get_drive_file_content' by specifying Chat context.

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 provides no guidance on when to use this tool versus alternatives like 'get_gmail_attachment_content' or 'get_drive_file_download_url'. It mentions mode-specific behavior but lacks explicit usage recommendations or exclusions.

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