list_models

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

The description adds useful behavioral info beyond the readOnlyHint annotation, such as being free and requiring no API key, and specifies the returned information (strengths, ratios, resolutions, reference limits). No contradictions.

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 sentences concisely state the purpose and an important usage detail (free, no API key). No superfluous content.

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 simple read-only listing tool with one parameter and no output schema, the description adequately covers what it does and returns. It does not mention pagination or limits, but that is likely acceptable for this tool.

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 description coverage is 0%, but the description clarifies that the mediaType parameter filters by image/video/all, adding meaning beyond the enum values in the schema. The single parameter's purpose is well explained.

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 tool lists LemGen models with specific attributes (strengths, ratios, resolutions, reference limits). It distinguishes from sibling tools which are about generation, enhancement, and search.

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 implies usage for listing models but does not explicitly state when to use this tool versus alternatives or when not to use it. The context of sibling tools makes it the only list tool, but explicit guidance is lacking.

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