list_attachments

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

No annotations are provided, so the description carries the full disclosure burden. It does not state that this is a read-only, non-destructive enumeration, nor mention ordering, pagination, or behavior on emails with no parts, for a tool that the agent must be able to call safely.

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?

A single efficient sentence with the enumerating verb front-loaded and no filler. It is appropriately sized, though the parenthesis adds clarification at the cost of a slightly denser read.

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 presence of an output schema means return values needn't be explained, which offsets some gaps. However, with no annotations and an undocumented required path parameter, the definition is only minimally sufficient for a read tool with ambiguous input.

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 0% and the single parameter "path" is undocumented in both schema and description. "Of one email" hints that path identifies the email, but the format (filesystem path, ID, URI) is left ambiguous, which is a real risk for a required parameter.

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?

States a specific verb (List) and resource (MIME parts: attachments, inline images, bodies) of a single email, and parenthetically disambiguates what a "MIME part" is. It does not distinguish the tool from siblings like open_attachment or view_emails, but the core purpose is 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?

No when-to-use guidance, no prerequisites, and no mention of alternatives (e.g., open_attachment to fetch the actual content). Usage is only weakly implied by "of one email," so the agent must infer both trigger conditions and relationships to siblings.

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