Delete tokens

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

Goes well beyond the annotations by disclosing that actors remain in the actor directory, unlinked tokens lose their own values, the operation is atomic when an id is missing, and the response lists deleted and failed tokens. This adds meaningful behavioral context beyond the destructiveHint and idempotentHint annotations.

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 dense sentences, each earning its place: the core action, the side effect on actors, the atomic failure behavior, and the response contents. The most important information is front-loaded in the first sentence.

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 only two parameters and no output schema, the description fully covers what an agent needs: scene targeting, id-only restriction, side effects, failure atomicity, and response contents. Nothing essential is missing.

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 100%, so the baseline is 3. The description adds extra semantic value by clarifying that tokenIds must be ids only, that sceneIdentifier can target a scene by id or name, and that the active scene is used when omitted. This enriches the parameter meaning beyond the schema alone.

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?

States a specific verb and resource: 'Remove tokens from the active scene (or the scene in sceneIdentifier), by their ids only.' It clearly distinguishes this from sibling tools like move-token or update-token by emphasizing id-based removal and scene 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?

Provides clear context for when to use it: when removing tokens from a scene by id, with an optional sceneIdentifier for targeting a non-active scene. It does not explicitly name alternatives, but the scope and conditions are unambiguous enough for an agent to select it correctly.

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