autoflow_get_recent_assets

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

With no annotations, the description must carry the behavioral burden, but it only states the action. It does not clarify what 'recent' means, whether partial or failed generation assets are included, whether the list is ordered or limited, or what the return structure looks like.

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?

The description is one sentence, starts with the active verb, and contains no filler. It is front-loaded and immediately communicates the core operation.

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 definition is usable for a no-parameter list tool but lacks the semantics of 'recent', any description of the output shape, and explicit differentiation from sibling tools. Given no output schema, the agent still has to guess return details.

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?

The tool accepts zero parameters, so the schema is trivially complete. The description adds domain context by identifying what the returned items are (video and image assets), which is enough for a parameterless tool.

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 names the specific operation ('scan and list') and the resource ('recent video and image generation assets... on Google Flow project canvas'). This is distinct from sibling tools such as autoflow_generate (creating assets) and autoflow_get_queue (queue items), so the agent can identify the correct tool immediately.

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?

No guidance is given about when to call this tool versus alternatives like autoflow_get_queue or autoflow_list_characters. There is no explicit 'when to use' or 'use this instead of' statement; the usage must be inferred from the resource name.

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