remove-from-actor

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

No annotations are provided, so the description carries the full burden. It discloses the GM-only restriction and the action of deletion from an actor. However, it does not clarify whether items are also permanently deleted from the world or just removed from the actor, which could affect agent reasoning.

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 concise two-sentence structure: the first sentence covers purpose and parameter options, and the second provides a key usage hint. No redundant or unnecessary words.

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 4 parameters (1 required) and no output schema, the description adequately explains how to identify items and constraints. It provides the prerequisite of using get-actor. However, it does not describe the return value or confirmation of deletion, but this is acceptable for a deletion tool.

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 each parameter already has a description. The tool description adds value by explaining how to use the parameters (e.g., 'itemNames are case-insensitive', 'Combine with type to disambiguate') and provides a usage hint ('Use get-actor to find item ids'). This exceeds the baseline of 3.

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 ('Delete items already on an actor'), the target (actor), and the method (by itemIds and/or itemNames, optionally constrained by type). It distinguishes from sibling tools like delete-item which deletes items globally.

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?

The description explicitly marks the tool as 'GM-only' and instructs to 'Use get-actor to find item ids,' providing clear context for use. However, it does not explicitly list when not to use this tool or mention alternatives such as delete-item for global deletion.

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