remove_item

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'Remove' implies a destructive operation, it doesn't specify whether this is permanent deletion, transfer to another location, or temporary removal. No information about permissions, side effects, or what happens when quantity exceeds inventory count is provided.

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, efficient sentence that immediately communicates the core function. There's no wasted verbiage or unnecessary elaboration, making it easy to parse while conveying the essential action.

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 destructive operation tool with 4 parameters, 0% schema coverage, no annotations, and no output schema, the description is inadequate. It doesn't address critical questions about the nature of the removal, error conditions, return values, or how it differs from similar inventory management tools.

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?

With 0% schema description coverage for 4 parameters, the description doesn't add any parameter-specific information beyond what's implied by the tool name. The baseline is 3 since the description doesn't compensate for the schema gap, but it doesn't actively mislead about parameters either.

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 ('Remove') and target ('an item from a character's inventory'), making the purpose immediately understandable. It doesn't explicitly differentiate from sibling tools like 'delete_item' or 'steal_item', but the specific context of character inventory provides some distinction.

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 provides no guidance on when to use this tool versus alternatives like 'delete_item', 'transfer_item', or 'steal_item'. There's no mention of prerequisites, appropriate contexts, or what distinguishes this removal operation from other inventory modifications.

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