Venice Character Chat

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

Without annotations, the description carries the full burden. It discloses two key behavioral traits: the authentication split (API key for lookup, x402 for chat) and content policy ('NSFW prompts allowed where the model permits'). This adds value beyond the schema, though it omits details like rate limits or data handling.

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 is two sentences plus a note, front-loaded with the core purpose. Every sentence adds value without redundancy, making it highly concise and efficient.

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 tool with 5 parameters and no output schema or annotations, the description is incomplete. It does not explain the return format or message structure, and lacks guidance on constructing inputs. The auth context is useful, but overall completeness is insufficient.

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%, so the description must compensate. It implicitly covers character_slug via 'by slug' but provides no explanation of model, messages, max_tokens, or temperature. The description fails to add meaningful parameter semantics beyond schema.

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 the tool's purpose: 'Chat with a Venice character by slug.' It specifies the resource (character) and action (chat), differentiating it from sibling tools like venice_chat (generic chat) and venice_list_characters (list only).

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 provides context on when to use: for character-specific chats. It notes the API-key requirement for character lookup and x402 support for chat completion, guiding users with different authentication methods. However, it does not explicitly exclude scenarios or mention alternatives beyond the auth note.

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