subtract_product

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

With no annotations, the description carries the full burden of behavioral disclosure. It mentions 'reloaded for this session,' which hints at a data-loading behavior, but does not state whether the operation is read-only, what happens with missing keys, whether order matters, or what the return value looks like. This is a significant gap for a set operation with no schema coverage.

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, front-loaded sentence with no fluff. It directly states the purpose and the key identification mechanism. It is appropriately concise, though it could have added more detail without losing conciseness.

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 set-operation tool with two array parameters, no annotations, and no output schema, the description is notably incomplete. It does not explain the result format, error behavior, or edge cases (e.g., duplicate keys, empty sets). An agent would need to infer too much to call it correctly and interpret the outcome.

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 schema provides two arrays of strings with no descriptions (0% coverage). The description clarifies that these arrays are 'identified by primary keys,' giving meaning to the parameters. However, it does not explain the exact semantics of left vs. right (e.g., which is the base set) or any formatting requirements. It partially compensates for the schema gap but not fully.

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 states the action (subtract) and the resource (Product sets), and clarifies that they are identified by primary keys. It differentiates from siblings because it targets Product specifically, though it doesn't explicitly contrast with union/intersect. The meaning of 'subtract' is implied but not formally defined (e.g., set difference), so it's clear but not fully precise.

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 implies this tool is for subtracting Product sets, which inherently distinguishes it from union/intersect and from other entities. However, it does not explicitly state when to use it over alternatives or provide exclusions. The context is clear enough for an agent to infer usage, but lacks explicit guidance.

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