List VicSee models

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

Annotations already signal readOnlyHint and openWorldHint, so the agent knows the tool is safe and non-destructive. The description adds useful context by stating the output includes capabilities and credit costs, and reaffirms the read-only nature. No contradictions or missing behavioral traits for a simple list tool.

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 consists of two concise sentences. The first clearly states the purpose, and the second provides a crucial usage hint and optional filter. Every word adds value with no redundancy.

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?

Given the tool's simplicity (one optional param, no output schema), the description adequately covers the tool's role and output. It mentions that the output includes model id, capabilities, and credit costs. No mention of pagination or error cases, but for a straightforward listing tool, the description is sufficiently complete.

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 100%; the only parameter 'type' is described in the schema as 'Filter by media type.' The description merely echoes this with 'Optionally filter by media type,' adding no new meaning beyond the schema. Baseline of 3 is appropriate.

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 the tool lists available VicSee models with their capabilities and credit costs. It also explicitly indicates that this should be called first to obtain a model ID for vicsee_generate, distinguishing it from sibling tools.

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 guidance to 'Call this first to find a model id to pass to vicsee_generate,' which is a strong when-to-use instruction. It also mentions optional filtering by media type, but does not provide explicit when-not-to-use or alternative tool scenarios, though sibling context makes alternatives clear.

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