create_actor

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

With no annotations, the description must carry the behavioral burden. It discloses a key behavior (defaults to linear stat growth unless a parameters Table is provided), which adds context. However, it introduces an undeclared 'parameters Table' not present in the schema, and lacks details on side effects or permissions.

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 concise sentence, front-loaded with the action verb, and no unnecessary words. It efficiently communicates the core purpose.

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?

Despite the complexity of a 15-parameter creation tool, the description is sparse. It explains a default behavior but omits return values, prerequisites, or clarification of the 'parameters Table' reference. The schema partially compensates, but the description lacks sufficient context for reliable 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?

Schema description coverage is 53%, so the description should compensate for the undocumented parameters. It only vaguely references 'parameters Table' and 'defaults', adding little semantic value to the 15 parameters. The provided parameter descriptions in the schema do most of the work.

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 action ('Create a new actor') and resource, distinguishing it from sibling tools like update_actor or search_actors. It also adds specific default behavior (RMXP defaults, linear stat growth curves), providing a clear 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?

Usage is implied by the verb 'Create' but there is no explicit guidance on when to use this tool versus alternatives, such as update_actor for modifications or get_actors for retrieval. No exclusions or conditions are mentioned.

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