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

Annotations already declare readOnlyHint=false, idempotentHint=false and destructiveHint=false, but the description adds genuinely new context: stock levels and cost are mutated, and there is no undo available through this API. That irreversibility warning is the most important thing an agent needs to know for a write tool. It still omits permission requirements, duplicate-submission risk (relevant given idempotentHint=false), and error 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?

Four short sentences, front-loaded with the WRITE marker and the additive behavior, then line structure, then the risk warning, then the endpoint. Every sentence carries distinct information with no repetition of the schema or title.

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 non-idempotent write tool with no output schema, the description covers what is mutated and that it cannot be reversed, which is most of what an agent needs. It falls short on what happens on failure or retry (important since the operation is not idempotent) and on how to identify offices, which siblings like bsale_list_offices would supply.

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?

With 60% schema coverage, the description compensates by explaining the mutually-exclusive identification semantics for each detail line (variant by id, SKU code or barcode) — a constraint the schema does not encode with any oneOf. It still leaves note, document and document_number unexplained beyond their short schema blurbs.

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?

States a specific verb and resource ('record a stock reception') plus the precise effect ('ADDS quantities to an office's inventory'), which is exactly what separates it from the read-only siblings like bsale_list_stocks. The parenthetical Spanish term and the WRITE prefix remove any ambiguity about operation type.

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?

'Confirm the numbers first' implies a precondition before invoking, which is useful usage context. However, no alternatives are named and there is no explicit statement of when-not to use this (e.g. for transferring between offices or correcting a prior reception), so the guidance remains implied rather than explicit.

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