List attachments

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds the genuinely useful ordering behavior ('newest first'), but says nothing about pagination despite a page_token parameter, nor about how the memo scope interacts with result limits.

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 sentence carries both operating modes, the filter dimensions, and the sort order, with no filler. The primary scoping choice (one memo vs global search) is front-loaded.

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?

For a read-only, idempotent list tool with rich annotations and no output schema, the description covers modes, filters, and ordering adequately. The only real gap is pagination/limit behavior, which an agent would need in order to page through results.

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 71%, with substantive descriptions on memo, type, creator, filename, and unlinked_only. The description reinforces the filterable dimensions (file name, MIME type, unlinked status) but adds no syntax, defaults, or paging detail beyond the schema, so the baseline 3 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 names a specific verb (List) and resource (attachments) and spells out the two operating modes: scoping to one memo versus searching all attachments by filename, MIME type, or unlinked status. It also states the default ordering (newest first). It never names a sibling to contrast with, so it stops just short of full sibling differentiation.

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 'of one memo, or search all your attachments' construction makes the two usage contexts explicit, and the precedence rule (memo wins over other filters) is stated in the schema. There are no exclusions or pointers to alternative tools for fetching attachment content (e.g. download_attachment/read_attachment).

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