list_assets

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 discloses that the registry is in-memory, clears on restart, and records expire after a configurable TTL, which is good behavioral context. It does not explicitly state that the tool is read-only, but 'list' implies no side effects.

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 concise sentences that front-load the core purpose and then add necessary context about registration and expiration. Every sentence adds value with no redundancy.

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?

The description lacks details about the return format or fields of assets, and there is no output schema. While the tool is simple, the description could be more complete by indicating what properties each asset includes.

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 parameters are already well-documented in the schema. The description does not add additional meaning beyond what the schema provides; it only gives broader registry context. 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 clearly states the verb 'List' and the resource 'recently generated assets from the in-memory registry' with sorting order 'newest-first'. It distinguishes from siblings like 'list_output_images' by specifying the registry context.

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 description explains when assets are registered (workflow completion) and their ephemeral nature (TTL and server restart), giving context for usage. However, it does not explicitly state when not to use this tool or name alternatives, though the context implies it for completed workflow assets.

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