Download Chat Attachment

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

Annotations provide limited hints (not read-only, not destructive). The description adds valuable behavioral details: file path vs temporary URL based on mode, and URL expiration. 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?

Two sentences, front-loaded with main purpose, second sentence adds essential mode details. No unnecessary words or repetition.

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?

Given the tool has 3 parameters with schema descriptions and an output schema, the description adequately covers behavior and return values. Lacks details on authorization requirements or edge cases, but overall sufficient.

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?

Input schema covers 67% of parameters with descriptions. The tool description does not add any parameter-specific meaning beyond what the schema provides. The user_google_email parameter lacks description both in schema and description, so baseline score applies.

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 tool downloads an attachment from a Google Chat message and saves it to local disk. The verb 'download' and resource 'attachment from a Google Chat message' are specific and distinct from sibling tools like get_gmail_attachment_content or get_drive_file_download_url.

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 clarifies mode-specific behavior (stdio vs HTTP) and mentions URL validity duration. However, it does not explicitly state when to use this tool over alternatives, though the tool name and context make the usage clear.

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