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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered and the description adds nothing behavioral on top of it — no caching, no auth requirement, no note that the catalog is static versus dynamic. It does disclose that the result includes modes and aspect ratios alongside models, which is modest added value, but not a behavioral trait beyond the annotation coverage.

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 purpose is correctly front-loaded in sentence one, but sentence two is a seventeen-item model roster that is volatile data and, with an output schema present, duplicates what the tool returns. That roster consumes the majority of the text without changing how an agent selects or invokes the tool.

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, read-only catalog tool with an output schema, return values need not be explained, so the definition is functionally callable. What is missing is the surrounding context an agent needs — namely that this catalog feeds model selection in generate_image_lab or quote_image_lab — leaving the tool adequately described but not well placed in the workflow.

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 takes zero parameters, which is the baseline-4 case. Schema description coverage is 100% and there is nothing for the description to disambiguate, so no penalty is warranted.

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 first sentence gives a specific verb and resource ("List Image Lab models, modes, and aspect ratios") and the name plus resource scope cleanly separates it from list_image_lab_generations, which lists past runs rather than the catalog. The "Same catalog as /image-lab" aside is a routing note, not purpose, and the rest of the text is content enumeration rather than further purpose definition.

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?

There is no statement of when to call this versus alternatives, even though the sibling set contains obvious consumers (generate_image_lab, quote_image_lab, list_image_lab_generations). The only contextual hint is "Same catalog as /image-lab," which implies equivalence but never says the tool should be called to discover valid model identifiers before generating or quoting.

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