replicate_list_models

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

With no annotations, the description carries full burden for behavioral disclosure. It states 'List public models' implying a safe read operation, but fails to mention pagination (cursor parameter), rate limits, response structure, or any side effects. The description adds minimal value beyond the inferred read-only nature.

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 a single concise sentence, but it omits important details that would justify its brevity. It is not verbose, but it is under-specified, sacrificing completeness for conciseness.

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 listing tool with two parameters and no output schema, the description is too minimal. It fails to explain pagination via cursor, the authentication requirement, or the nature of the returned data. The tool's complexity is low, so a complete description could easily cover these points.

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%, so the description must compensate. It does not mention either parameter: api_token (required for authentication) or cursor (for pagination). The agent must rely solely on the schema names, which lack any descriptive context.

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 verb 'List', the resource 'public models', and the scope 'on Replicate'. It distinguishes this tool from sibling Replicate tools like replicate_get_model (single model) and replicate_list_predictions (list predictions), as well as from similar list_models tools from other providers.

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 no guidance on when to use this tool versus alternatives. It does not mention use cases, prerequisites (e.g., authentication implied by required api_token), or scenarios where listing models is appropriate, such as before creating a prediction.

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