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

Annotations flag destructive/non-idempotent, but the description is what explains why: the call spends prepaid credits, and it names the two tools that reveal cost and balance before committing. That is genuine context beyond the hints. It does not say whether a failed creation refunds credits or what the created record contains, which keeps it from a 5.

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?

Three tight clauses: cost/credit routing first, then purpose, then parameters. Every sentence carries information an agent needs, and nothing is repeated from the annotation block.

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 never says what a successful creation returns — a character id, an image, or an async job that must be polled via kreavo_check_image_status. For a credit-spending creation tool that is a meaningful gap, though the cost and parameter coverage is solid.

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 coverage is 0% — no parameter descriptions and no declared enum — so the description carries the full burden, and it does list all three params with the model being optional plus the allowed values (nano-banana-2|nano-banana-pro|nano-banana). Guidance on what a good physical_description should contain, or name constraints, is 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?

"Create an AI influencer from a physical description (no image needed)" gives a specific verb plus resource and immediately distinguishes it from the image-based siblings (kreavo_generate_image, kreavo_image_edit, kreavo_upload_image). An agent can route here without opening any schema.

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 "no image needed" clause tells the agent when this path is appropriate versus image-driven tools, and the description routes to kreavo_list_models for cost and kreavo_get_credits for balance before spending. It stops short of naming an explicit alternative or exclusion (e.g. versus kreavo_generate_photoshoot).

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