replicate_list_models

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds nothing beyond that: it never mentions that results are paginated via cursor, that an API token is required for auth, or how large a page is — all behaviorally relevant for this call.

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?

A single front-loaded sentence with no filler. It is terse to the point of leaving gaps, but nothing written is wasted.

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?

There is no output schema, no parameter documentation, and no mention of pagination or result shape. For a listing endpoint driven by an opaque cursor, the description should at minimum note that repeated calls with the returned cursor enumerate the catalog.

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%: neither api_token nor cursor carries any schema text. The description does not compensate — it never explains that cursor is a pagination token for fetching subsequent pages, nor what api_token permissions are needed. This is the weakest area for a 2-parameter tool.

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?

States a specific verb ('List') and resource ('public models available on Replicate'), so an agent knows exactly what it returns. It does not distinguish itself from related siblings such as replicate_get_model or the several other *_list_models tools in the catalog, but the resource is unambiguous.

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 indication of when to call this versus replicate_get_model (which fetches a specific model's details) or how it relates to replicate_create_prediction. The 'public' qualifier hints at scope but no exclusion or alternative is stated.

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