Venice List Characters

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

Discloses authentication behavior (API key required) beyond missing annotations, but lacks details on pagination, response structure, or what 'public' entails.

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?

Extremely concise—two sentences, front-loaded with purpose, no redundant information.

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 4 parameters, no output schema, and no annotations, the description is insufficient. It omits parameter semantics, expected output, and comparisons to sibling tools.

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?

No parameter descriptions are provided despite 0% schema coverage. The description does not explain the purpose of tag, limit, offset, or search parameters.

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?

Description clearly states the tool lists public Venice characters, which is a specific verb+resource. It distinguishes from sibling tools like venice_chat_with_character and venice_list_models.

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?

Description provides authentication constraint (API key required, not x402 wallet auth) but does not explicitly state when to use this tool versus alternatives like searching or filtering characters.

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