Get Received Email Attachment

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

No annotations are provided, so the description carries full behavioral burden. It discloses that the download URL is time-limited, which is a key behavior, but does not mention other aspects like authentication requirements, what 'details' are returned, or URL expiration duration.

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 a single sentence that is concise and front-loaded, conveying the essential purpose and key feature (time-limited URL) with no extraneous words.

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 no output schema, the description partially explains what is returned (details and a download URL), but does not enumerate what 'details' entail. However, the sibling context and tool name provide enough context for an agent to infer typical attachment metadata. Slight gap in completeness.

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 100% with both parameters described as 'The attachment ID' and 'The received email ID'. The description adds no extra meaning beyond these schema descriptions. Baseline for high coverage is 3.

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 retrieves details of a specific attachment from a received email, including a time-limited download URL. It distinguishes from sibling 'get-sent-email-attachment' by specifying 'received email', and from 'list-received-email-attachments' by being a single-item retrieval.

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 (e.g., list-received-email-attachments or get-sent-email-attachment). No prerequisites or context for when it is appropriate are mentioned.

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