Get Pollinations Model Details

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

Beyond the readOnly/idempotent annotations, this description reveals important behavioral traits: the 15-minute in-memory cache behavior, the ability to bypass it with refresh=true, and that refresh refetches /image/models first. It also states the return value is full metadata, which adds transparency about what the agent will receive.

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 well-organized: it opens with the core purpose, follows with usage context, then a structured args list, and closes with returns and fallback behavior. Every sentence carries necessary information, and the structure makes it easy to scan.

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 lookup tool, this description is complete. It covers purpose, usage timing, cache/refresh behavior, response format options, return value, and a failure fallback action. The lack of an output schema is acceptable because the description clarifies that full metadata is returned and gives examples of the fields involved.

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 schema covers all parameters with descriptions (100% coverage), so the baseline is 3. The description adds value by giving concrete model examples (nanobanana, p-image-edit, ltx-2) and specifying that refresh refetches /image/models, which is a detail not present in the schema. This modestly elevates it above the baseline.

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 that this tool retrieves full metadata for a single Pollinations image or video model by name or alias, using the specific verb 'Get' and a specific resource. It differentiates itself from siblings by mentioning it is used after pollinations_list_models for detailed information, and it lists exact fields like pricing and capabilities.

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 gives explicit usage guidance: 'Use this after pollinations_list_models when an agent needs exact pricing, capabilities...' It also provides a fallback instruction: 'If no model matches, call pollinations_list_models with a broader search.' This clearly indicates when to use this tool versus alternatives.

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