manage_character

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

Annotations provide no positive safety context (all hints false), and the description doesn't disclose that many actions mutate existing assets, require specific parameters, or produce side effects. It only mentions creation, which is a subset of the tool's actual behavior, leaving destructive or modifying actions unmentioned.

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?

A single sentence with no wasted words, front-loaded and easy to parse. However, it sacrifices necessary content for brevity, underspecifying a highly complex tool. It's structurally clean but not appropriately sized for the tool's scope.

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 74 parameters, 27 enum actions, nested objects, and no output schema, this description is grossly inadequate. An agent cannot determine how to select actions, which parameters are required for each action, or what the tool returns, making it nearly unusable for correct invocation.

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 schema has 74 parameters with 69% description coverage, but the description adds no parameter-level semantics beyond vague categories like 'movement' and 'animation state machines'. It doesn't explain which parameters apply to which actions or highlight dependencies like required action enum and modeId.

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 clear action ('Create Character Blueprints') but is too narrow for a tool whose action enum includes configuration, movement, footstep, and query operations. It partially distinguishes from generic manage_blueprint by focusing on character-specific elements, but the verb 'Create' underrepresents the tool's broader management scope.

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?

No explicit guidance on when to use this tool vs alternatives like manage_blueprint or manage_skeleton. The description implies use for character blueprint creation, but it doesn't mention exclusions or where to go for generic blueprint tasks, leaving usage boundaries vague.

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