inventory_create_transfer

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 states 'Create' which implies a write/mutation operation, but doesn't disclose critical traits like required permissions, whether the transfer is immediate or pending, if it affects inventory counts instantly, error conditions (e.g., insufficient stock), or side effects. This leaves significant gaps for an agent to understand the tool's behavior.

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 front-loads the core action ('Create an internal stock transfer between locations') with zero wasted words. Every element earns its place by specifying the action, resource, and scope concisely.

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 complexity of a creation tool with 4 parameters, no annotations, and no output schema, the description is incomplete. It lacks information on behavioral aspects (e.g., mutation effects, error handling), usage context, and output expectations. While the schema covers parameters well, the overall tool understanding remains inadequate for safe and effective use by an agent.

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 description coverage is 100%, so the schema already documents all parameters thoroughly (e.g., 'from_location_id' as 'Source location ID', 'products' as 'Products and quantities to transfer'). The description adds no additional parameter meaning beyond what's in the schema, such as explaining relationships between parameters or usage examples. Baseline 3 is appropriate when the schema does the heavy lifting.

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 verb ('Create') and resource ('internal stock transfer between locations'), making the purpose unambiguous. It distinguishes from sibling tools like 'inventory_get_stock' or 'inventory_list_operations' by specifying a creation action rather than retrieval. However, it doesn't explicitly differentiate from other creation tools like 'manufacturing_create_order' or 'sales_create_order' beyond the domain context.

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?

No guidance is provided on when to use this tool versus alternatives. The description doesn't mention prerequisites (e.g., needing valid location IDs or product availability), exclusions (e.g., not for external transfers), or related tools (e.g., whether 'inventory_list_operations' might show past transfers). Usage is implied only by the tool name and description context.

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