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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, and the description's 'Read-only' merely restates that. The one piece of added value is disclosing that in-progress tasks are returned alongside finished assets, but it says nothing about ordering, counts, or freshness of task status.

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?

Three short sentences, front-loaded with the resource and its contents. 'Takes no arguments' and 'Read-only' duplicate the empty schema and readOnly annotation, so they are slightly wasted 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-shape explanation is unnecessary, and the description covers both finished and running items. A note on how running tasks are surfaced or ordered would make it fully complete.

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?

Zero parameters, so the baseline applies; 'Takes no arguments' is consistent with the empty schema and correctly tells the agent nothing must be supplied.

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 ('Show the works generated in this chat') and enumerates the contents: finished images and videos plus still-running tasks. The 'in this chat' scoping clearly separates it from global siblings like get_tasks and list_recent_tasks.

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?

Gives a clear selecting condition: 'Use when the user wants to see what was made in this conversation.' However it never names the near-twin alternatives (get_tasks, list_recent_tasks) or says when those are preferred instead.

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