replicate_model

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered without description help. The description adds little behavioral context beyond the default-value hint and the shape of the returned input list; it says nothing about auth requirements, rate limits, or failure modes for an open-world 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?

It is short, but it is two loosely joined fragments that are not front-loaded with a clear action. The parenthetical list and the trailing clause mix return-value description with invocation advice, so brevity does not translate into clarity.

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 single-parameter, read-only lookup with no output schema, the description conveys roughly what comes back and the default behavior. However, it omits any routing guidance among the several Replicate-related siblings and never states the action plainly, leaving a small but real gap.

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 coverage is 100% and the schema already documents the 'model' parameter format ('owner/name, e.g. bytedance/seedance-2.5'). The description adds meaning beyond the schema by explaining that omitting model yields the default, which clarifies the optionality semantically rather than just syntactically.

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 is a sentence fragment that describes what the tool returns (a model's inputs: type, default, allowed values) rather than starting with a clear verb+resource. An agent can infer this is a lookup that returns a model's input schema, but the phrasing 'so a job can set what the user asks for' is confusing boilerplate. It makes no attempt to distinguish itself from close siblings like replicate and replicate_status.

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 only guidance offered is 'Leave model out for the default,' which addresses one parameter case rather than when to call this tool. There is no indication of when to prefer replicate_model over replicate, replicate_status, or run_job, leaving the agent to guess in a crowded Replicate-related sibling set.

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