place-tokens

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

With no annotations, the description fully explains how tokens are built from prototypes with overrides, and that actors can be repeated. It could mention immediate placement or scene activation, but overall transparent enough.

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?

Four well-structured sentences front-loading the purpose, followed by details. No fluff, every sentence adds value.

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?

Lacks output schema, but the tool is a command with no return value expected. The description covers input behavior well. Could mention result or side effects, but adequate for the tool's complexity.

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 description adds significant meaning beyond the schema: it explains that tokens inherit prototype defaults, that 'actor' accepts ID or exact name, and coordinates are in absolute canvas pixels. This enriches the schema's descriptions.

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 places actors' tokens on a scene, using batch encounter prep as an example. It distinguishes from sibling tools like create-tokens or update-token by focusing on placing from prototypes in bulk.

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?

Explicitly states that this is for scripted/batch placement, contrasting with manual dragging in the app. Also specifies GM-only access, giving clear usage context.

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