list_assets

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

With no annotations, the description discloses ephemeral nature (clears on restart, expires after TTL). Does not explicitly state read-only behavior, but 'list' implies non-destructive. Adds useful lifetime information.

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 concise sentences. First sentence front-loads purpose and ordering. Second sentence covers registration and lifetime. No redundant 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?

Adequately covers behavior (ordering, registration, expiration) for a list tool with two optional filters. No output schema, but description doesn't detail returned fields; still sufficient for the tool's simplicity.

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 descriptions for both limit and since. The tool description adds no extra meaning beyond the schema, so 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?

Clearly states verb 'List', resource 'recently generated assets from the in-memory registry', and ordering 'newest-first'. Distinguishes from sibling tools like list_output_images by specifying 'assets from registry'.

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?

Provides clear context: assets registered after workflow completion, expiry after TTL. Missing explicit when-not-to-use or alternative tool references, but context is sufficient for typical use.

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