Summon actor

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

With no annotations provided, the description carries the full burden of disclosing side effects. It only states that an actor is spawned at the player's position, but does not mention whether this is persistent, what happens if the class name is invalid, whether spawn limits apply, or any other consequences. It also doesn't explain the meaning of 'kind' or 'instance' in behavioral terms.

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 a single sentence that immediately identifies the action and target. There is no fluff or redundant wording, and it is front-loaded with the verb 'spawn'. It earns its place perfectly.

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 three parameters, no output schema, and no annotations, the description is too sparse. It doesn't explain what the tool returns after summoning, how 'kind' affects resulting behavior, or what happens if an invalid class is used. An agent would lack sufficient information to safely invoke this tool without additional research.

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 clarify all parameters. It indirectly explains className ('given class') and provides useful context for why no position parameter exists (spawns at player's position). However, it provides no meaning for 'kind' (normal/friend/foe) or 'instance' (count?), and does not interpret the enum or default values.

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 uses the specific verb 'spawn' to identify the action, names the resource as 'an actor of the given class', and specifies the location as 'the player's position'. This clearly distinguishes it from sibling tools like give/take (item manipulation) and list_actor_classes (querying).

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?

There is no guidance on when to use this tool or when to prefer alternatives. For example, it doesn't mention that list_actor_classes should be called first to find valid class names, nor does it explain differences between summon and give or actors_near. No exclusions or prerequisites are provided.

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