download_chat_attachment

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

No annotations are provided, so the description carries the behavioral disclosure burden. It does well by explaining mode-dependent behavior: stdio returns a local file path, HTTP mode returns a temporary URL valid for 1 hour. It also documents the default attachment_index. It does not mention error cases or authentication requirements, but it provides solid transparency about output behavior.

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 well structured with a clear opening sentence, mode-specific behavior, an Args section, and a Returns section. Every sentence provides useful information, and there is no filler or 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 tool is relatively simple, but the missing required user_google_email parameter is a notable completeness gap. The description gives return behavior and mode differences, but an agent cannot fully understand all required inputs without that parameter context. Still, the core usage and output are sufficiently described for a basic download tool.

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 0%, so the description must compensate. It explains message_id with a format example and attachment_index with zero-based/default semantics, but it completely omits the required user_google_email parameter. Since a required parameter is left undocumented, the description only partially compensates for the schema's lack of descriptions.

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 states a specific verb and resource: 'Downloads an attachment from a Google Chat message and saves it to local disk.' This clearly distinguishes it from siblings like get_gmail_attachment_content, which handles Gmail attachments, and get_drive_file_download_url, which handles Drive files. The resource and action are unambiguous.

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 makes clear that the tool is for Google Chat attachments, which implies when it should be used, but it does not explicitly mention alternatives or exclusion conditions. With siblings handling Gmail attachments and Drive downloads, explicit routing guidance would strengthen this dimension. The usage context is implied rather than stated.

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