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

With zero annotations the description must carry the full burden, and it does real work: it discloses the permission level ('Any member'), the failure mode and status code ('Refused with 409 when it would take the count below 0'), and the sign convention per kind. It stops short of saying whether entries are reversible or how a movement relates to existing counts.

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?

Four short sentences, front-loaded with the action and then the quantity/kind rules, then the failure condition, then permissions. No filler and nothing repeated from the schema.

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?

An output schema exists, so return values need not be described, and the description covers the mutation's key risks (negative-stock rejection, who may call it). What remains missing is any statement about job_id and item_id being undocumented elsewhere, and whether a correction is possible after posting.

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?

At 20% schema coverage the description compensates partially: it explains the sign semantics of quantity and the directional effect of each kind value, which the enum alone does not. But three of five parameters — notably job_id (presumably ties the movement to a job) and pricebook_item_id (the 'tracked material' reference) — get no explanation anywhere, leaving a real gap.

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 gives a specific verb and resource — recording a stock movement of one of five named kinds against a tracked material — which clearly separates it from reads like stock_list/stock_moves. It never names those siblings or stock_setLevel (absolute level setting) as the alternatives, so an agent must infer the boundary rather than being told it.

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 five kinds are enumerated and their directional effects explained (used/lost subtract, received/returned add, adjusted is signed), which implicitly tells the agent which kind to pick. However there is no explicit 'use this instead of X when Y' guidance against stock_setLevel or stock_moves, and no stated prerequisites for choosing a kind.

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