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

Annotations already declare this is a non-destructive, non-idempotent write to a closed-world resource, so the safety profile is known. The description adds nothing beyond that: no mention of duplicate-name handling, default values for optional fields, or what the created record includes.

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 single sentence is short but that brevity is under-specification, not conciseness. There is no front-loaded scope statement or useful content to be concise about.

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 10-parameter mutation tool with no output schema and no field descriptions, the definition gives an agent nothing needed to populate the schema correctly or predict the result. It is effectively unusable beyond the tool name.

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 0% across 10 parameters, and the description provides zero compensation. Critical ambiguity is unaddressed: whether quantity is initial stock, what unit means relative to quantity, what units the *_cents fields use, and why is_active is an integer rather than a boolean.

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 is a verbatim restatement of the tool name split into a sentence ('Create a stock_item'). It conveys no scope, no resource detail, and no differentiation from stock_item_update, stock_item_adjust, or stock_item_delete beyond the name itself.

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?

There is no guidance whatsoever about when to call this versus the sibling stock tools (e.g. adjust for quantity changes, update for edits), nor any preconditions such as required permissions or dependency on an existing category.

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