clickup_list_document_page_attachments

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

With no annotations, the description carries the full burden, and 'list metadata' does convey a read-only, non-destructive operation. However, it does not disclose pagination behavior, required access to the page/workspace, or that results are paginated metadata rather than file contents — details that matter for a zero-annotation tool.

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 front-loaded sentence with no wasted words; the key scope qualifier ('metadata') and the clarifying parenthetical come early. It is efficient, though the brevity contributes to the gaps noted elsewhere.

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?

With no output schema, the description should say what the returned metadata looks like (names, IDs, URLs, sizes), but it only says 'metadata.' Pagination is covered by the schema's cursor/limit, so the main missing piece is the shape of returned data for an otherwise simple list 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 coverage is 100%, so limit, cursor, page_id, and workspace_id are all documented in the schema, including the page_id discovery hint. The description adds no parameter meaning 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 uses a specific verb (list) with a clearly scoped resource (metadata for files attached to a ClickUp doc page) and clarifies the contents are images and files embedded in page content. It implicitly separates itself from the download sibling by emphasizing 'metadata' only, though it never names that sibling.

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 word 'metadata' implies this is for discovery rather than retrieval, hinting that downloading should use a different tool, but the description never states when to use this versus clickup_download_document_page_attachment. No prerequisites or exclusions are given, leaving usage to inference.

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