show_invokeai_gallery_card

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

With no annotations provided, the description carries the full burden. It discloses the return format (ToolResult with PrefabApp card and plain text fallback), which is useful. However, it does not mention error behavior, empty state, or other operational nuances, so transparency is partial.

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 extremely concise, front-loaded with the core action, and logically structured with a Return Format and Example sections. Every sentence adds value and there is no wasted text.

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 tool is simple, has one optional parameter, no output schema, and no annotations. The description explains what it does, the return format, and gives an example, which covers most practical needs. It lacks details about empty results or edge cases, but for a 'show card' tool, it is reasonably 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?

The input schema already provides a description for the 'limit' parameter with default, min, and max, and schema coverage is 100%. The description adds no extra semantic meaning beyond the example call, so the baseline of 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 states a specific verb ('Show') and resource ('most recent gallery images') and clearly distinguishes this from sibling tools like show_invokeai_queue_card or show_invokeai_models_card. However, it does not explicitly contrast with the sibling invokeai_gallery, which could also list gallery images, so it's clear but not fully differentiated.

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 on when to use this tool versus alternatives such as invokeai_gallery or other show_*_card tools. The description simply states what it does, leaving the agent to infer usage context.

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