Venice Character Chat

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

Annotations only give the generic safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=false), so the description carries the burden for auth behavior and content policy. It does this well, disclosing the x402-vs-API-key split for character lookup and the uncensored/NSFW-permitting nature of the endpoint. It stops short of describing streaming, billing implications, or return shape.

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 purpose is front-loaded in the first clause, followed by the auth caveat and content-policy note. Three compact sentences with no filler, though the em-dash aside is slightly dense.

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?

With no output schema, the description should say more about what comes back and how messages/model are used, which it does not. It does cover the two genuinely non-obvious facts (auth path and content policy), making it adequate but with clear gaps for a 5-parameter generation tool.

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% across 5 parameters, so the description must compensate and largely does not. It only gestures at character_slug ('by slug'); messages, model, max_tokens, and temperature get no explanation of format, defaults, or constraints beyond the raw JSON types.

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 states a specific verb and resource ('Chat with a Venice character by slug'), which is enough to distinguish it from the generic venice_chat sibling. It never explicitly contrasts itself with venice_chat or venice_responses, but the resource scope is unambiguous.

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?

It supplies one concrete usage prerequisite: character lookup is API-key-only while chat supports x402, so x402 users must fetch character info another way first. However, it never explicitly says when to prefer this over venice_chat, nor does it name venice_get_character/venice_list_characters as the lookup route, leaving the agent to infer the alternative.

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