Remove an item from one category

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It clearly states that the tool only unlinks, does not delete the item, and does not affect other category placements, which are the key behavioral traits. It does not mention edge cases like idempotency or error behavior, but for this simple operation the disclosure is strong.

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 two sentences long and front-loads the core action. The first sentence states the purpose, and the second adds a crucial distinction and an alternative. Every word earns its place without redundancy.

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 the simplicity of the operation and the lack of an output schema or annotations, the description covers the essential context: what it does, what it does not do, and which sibling tool to use for full deletion. It does not mention return values or failure modes, but those are not critical for this straightforward mutation.

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 input schema has 0% description coverage, so the description must compensate. While it does not explicitly map itemId and categoryId, the phrase 'item from a single category' makes the roles of both parameters inferable. The parameter names themselves are clear, but the description adds minimal additional semantic detail beyond the schema.

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 'Unlinks' to clarify the action, identifies the resource as 'an item' from 'a single category', and distinguishes this tool from both delete_item and remove_category. It explicitly differentiates it from sibling operations by clarifying that the item row and other category placements remain untouched.

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 explicit usage guidance by stating that delete_item should be used to remove the item everywhere, establishing a clear alternative. It also clarifies the scope of the operation (only unlinks from the specified category), giving the agent enough context to choose between this and related tools.

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