list_characters

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

With no annotations, the description carries the full burden. It states the tool lists characters and mentions a prerequisite: 'Requires connection to the full Creative Claw MCP server.' It implies a read-only operation by using 'List,' but does not explicitly state side effects or error behavior, though none are expected for a listing 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 is somewhat verbose and repetitive. Phrases like 'consistent multi-shot video production, UGC ads, and branded content' and 'maintain identity across generations' overlap in meaning, adding marketing fluff beyond the core purpose. A more concise wording would improve clarity.

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 no parameters and no output schema, the description is complete enough for invocation. It states the function, mentions the required server connection, and implies a list return. It lacks explicit error conditions but does not need them for basic usage.

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?

The tool has zero parameters, and the schema covers 100% (vacuously). Per the rubric, a 0-parameter tool receives a baseline score of 4. No parameter descriptions are needed, and none are missing.

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: 'List reusable Characters.' It distinguishes itself from sibling tools like list_models by specifying characters with persistent identities and optional voices, leaving no ambiguity about what is returned.

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 what the tool does but does not explicitly contrast it with alternatives (e.g., when to use list_characters vs list_models). While the purpose is clear, the lack of explicit when-not-to-use guidance reduces the score from a perfect 5 to a 3.

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