Venice List Characters

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

With no annotations provided, the description carries the burden of behavioral disclosure. It does state the authentication requirement (api-key only, no x402) which is a real behavioral constraint. However, it doesn't disclose pagination behavior, rate limits, or what the return structure looks like. The auth note is useful but the behavioral disclosure is incomplete.

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?

Two concise sentences with zero wasted words. The auth distinction is front-loaded and directly relevant. Every sentence earns its place.

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 4-parameter tool with no output schema and no annotations, the description should provide more guidance. No mention of pagination behavior, default limit behavior, what 'tag' filters on, or response format. The auth disclosure is helpful but doesn't compensate for the lack of parameter guidance and return information. Multiple sibling character-related tools exist, so more disambiguation is needed.

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% — the description explains NONE of the 4 parameters (tag, limit, offset, search). Each parameter's semantics are entirely undocumented. Names are somewhat self-explanatory (limit, offset, search), but 'tag' is ambiguous and none have type/format guidance beyond the schema. The description must compensate for the 0% coverage and does not.

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?

Clear verb+resource ('List public Venice characters'). The tool's purpose is unambiguous and the scope ('public') is specified. It distinguishes itself from venice_list_models and other list tools by naming 'characters' specifically, though it doesn't explicitly contrast with siblings like venice_chat_with_character.

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 explains WHEN it applies vs alternatives in terms of auth: 'api-key only, no x402' and explicitly states 'this endpoint does not accept x402 wallet auth.' This is a meaningful usage constraint. However, it doesn't say when to choose this over venice_chat_with_character or how the two relate, leaving some ambiguity for the agent.

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