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

Annotations already cover the read-only, non-destructive profile, and the description adds real context beyond them: the required content:read key scope and the newest-first ordering. It stops short of stating whether results are filtered by type (images vs files) or how paging terminates.

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 dense sentences with the resource and ordering front-loaded, followed by pagination details. The returned-field enumeration is justified because there is no output schema, though it makes the sentence list-like.

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 simple three-parameter read tool with no output schema, the description covers scope, ordering, returned fields, and paging adequately. Minor gaps remain around whether there's a total count for paging and whether asset type filtering is possible.

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 site, limit, and offset are already fully documented in the schema. The description restates the limit bounds and default and frames offset as paging, but adds no syntax or semantics beyond the schema baseline.

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 and resource ('List the site's uploaded images and files') plus ordering ('newest first'), which clearly separates it from entry/form/submission listing siblings. The returned field list further pins down what an 'asset' is.

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?

Usage is implied by the resource description, and the 'key scope content:read' note signals the prerequisite. However, it never says when to prefer this over adjacent tools such as read_draft_file, request_upload, or write_files, leaving the agent to infer.

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