get_last_image_info

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

With no annotations provided, the description carries full burden. It discloses key behavioral traits: it retrieves information about the 'last generated/edited image in this session,' implying session-scoped data and that it's read-only (consistent with 'get' verb). However, it doesn't specify what happens if no image exists or error conditions.

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 perfectly concise with two sentences that each earn their place: first states the core purpose, second provides crucial usage guidance. No wasted words, front-loaded with essential 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?

For a zero-parameter tool with no annotations and no output schema, the description provides good context about what information is retrieved and when to use it. However, it doesn't describe the return format or what specific fields (beyond 'file path, size, etc.') are included, which would be helpful given no output schema.

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 has 0 parameters with 100% schema description coverage. The description appropriately doesn't discuss parameters, maintaining focus on tool purpose. A baseline of 4 is appropriate for zero-parameter tools where no parameter documentation is needed.

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 specific verb ('Get information') and resource ('last generated/edited image'), specifying what information is retrieved (file path, size, etc.). It explicitly distinguishes this tool from its sibling 'continue_editing' by indicating this tool provides information needed for that operation.

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 provides explicit guidance on when to use this tool: 'to check what image is currently available for continue_editing.' It clearly connects usage to a specific sibling tool and context (checking availability before continuing editing).

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