Transfer stock to a job

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

Annotations already indicate destructive and non-idempotent behavior, but the description adds concrete detail: it changes bin quantities and can create job materials, inventory transactions, and job requirements. It also explicitly warns that retrying is unsafe, which is critical operational context beyond the annotations. No contradiction exists.

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 three short sentences - the purpose first, then effects, then a safety warning. Every sentence adds distinct information: what it does, what changes, and caution about retries. There is no fluff or redundancy, and the most important operational constraint (retry safety) is front-loaded after the purpose.

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?

This is a mutation tool with a single, opaque 'data' parameter and no documentation of its structure. The description covers side effects and retry risk, but it omits required inputs, expected format, or any clues about what constitutes valid data. Without that, an agent cannot reliably invoke the tool, making the description inadequate for the tool's complexity.

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 has zero description coverage, and the only parameter 'data' is an untyped, recursive object with no field documentation. The description does not explain what data should contain (e.g., job ID, stock details, quantities). With such low schema coverage, the description must compensate, but it provides no parameter guidance whatsoever, leaving an agent unable to construct a valid request.

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 a specific verb and resource: 'Transfer stock material to a job.' This clearly defines the operation and distinguishes it from siblings like 'update' or 'create' by focusing on the transfer-action semantics. The title and description align, leaving no ambiguity about the tool's purpose.

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 the use case (transferring stock to a job) but does not explicitly contrast with sibling tools or state when not to use it. There is no mention of alternatives or prerequisites, so an agent must infer from the name that this is the tool for stock transfers. It provides no conditions for selection.

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