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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds only that results carry posters for grid rendering — useful, but thin context beyond the structured fields, and it says nothing about ordering or pagination behavior despite an offset parameter.

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, no filler, with the scoping constraint front-loaded. The second sentence is compressed to the point of jargon ('list_generations with posters for the grid'), which costs a little clarity but not length.

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?

A read-only, non-open-world list tool with an output schema, so return-value explanation is unnecessary and annotations cover safety. The description supplies the audience/context distinction that structured fields can't express; only result ordering is left unaddressed.

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% with inline descriptions for kind, limit, since and offset, so the schema carries parameter meaning. The description adds no syntax, defaults, or format detail beyond what the schema already states (defaults and caps are in the schema). Baseline 3 is appropriate.

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 identifies the resource (generations, rendered as a poster grid) and distinguishes it from both list_generations (this one includes posters) and conversation-scoped tools. The verb is only implied via the sibling name 'list_generations', and the phrasing is telegraphic, but an agent can tell what it returns and where it belongs.

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?

Explicit exclusion: 'For the Veltake app's own screens only — not for a conversation.' That is a clear when/when-not split. It stops short of naming the conversation-side alternative (e.g. get_chat/list_generations in a chat context), so it's not a full routing statement.

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