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

No annotations are provided, so the description carries the full burden. It does disclose the sort order ('newest first'), which is genuine behavioral value beyond the schema, but it omits pagination behavior, default limit, and return shape for a list tool whose params are only half documented.

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 short sentences with zero waste; the core action and ordering are front-loaded ahead of the usage hint. Nothing could be cut without losing information.

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 annotations and no output schema, the description should at minimum resolve the project_id vs project_slug ambiguity and note pagination limits. It leaves an agent able to call the tool but uncertain about scoping and page traversal.

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 50%: project_id and project_slug are described in the schema, while limit and cursor are undocumented anywhere. The phrase 'a project's' weakly ties the call to the project parameters but does not clarify whether project_id and project_slug are alternatives or whether either is required (0 required params).

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 — listing images in a project's email image library — and adds the ordering (newest first). This clearly separates it from write-side siblings like upload_email_image and delete_email_image, though it never names them explicitly.

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 second sentence indicates downstream use ('lifecycle/workflow email `image` blocks'), which hints at context but is not a when-to-use rule. There is no guidance on when to choose this over list_email_templates or other listing tools, and no exclusion conditions.

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