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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower; the description still adds useful behavior beyond them: global scope across all projects, newest-first ordering, and cursor-based pagination with null meaning 'start at newest'. No rate limits or pagination end conditions are described, but the added context is real.

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 tight sentences, with the scope/ordering constraint front-loaded before the pagination mechanics. The phrase 'use next as before' is slightly compressed to the point of ambiguity but wastes no 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?

An output schema exists, so return values including the `next` cursor need not be re-explained. However, for a two-parameter, 0%-coverage schema, leaving `limit` entirely unaddressed makes the definition only minimally complete for a paginated 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 description coverage is 0% for both required parameters. The description does explain `before` semantically (null begins at the newest job), but says nothing about `limit` — no default, no sensible range — despite the schema allowing a nonsensical span from negative values up to 2^53. The reference to 'next' also assumes an output field name the caller must infer.

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+resource (list cloud exports) with ordering (newest first) and scope (across all projects), which helps separate it from list_projects and read_render. It does not explicitly name a sibling it excludes, but the scope phrase does the differentiation work.

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 'list this account's cloud exports' plus pagination instructions ('use next as before to fetch the next page'). There is no explicit when-to-use-vs-alternative guidance (e.g. read_render for a single job) or any note about when the list would be empty.

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