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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds the concrete endpoint paths and the interaction where lot/warehouse filters are ignored under by_warehouse, but says nothing about return shape, pagination, or precision of stock figures.

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?

A single dense sentence with the primary scope front-loaded, followed by the mode that changes behavior and the backing endpoints. Nothing is padded or repeated.

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 read-only query tool with no output schema, the description should indicate what comes back (e.g., quantity/unit per warehouse or lot). It covers inputs and endpoints but leaves the result contract entirely unspecified, which is a meaningful gap.

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 80%, so most parameters are already documented in the schema. The description restates the date, warehouse, lot and by_warehouse behavior without adding syntax, defaults, or edge cases beyond what the schema provides; baseline 3 applies.

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+resource ('Stock of one product') and the two supported modes (single warehouse/lot vs. per-warehouse breakdown), including the underlying endpoints. An agent can distinguish it from laudus_list_stock or laudus_product_kardex without opening a schema.

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 clarifies how the by_warehouse flag changes behavior, which implicitly guides usage, but it never says when to prefer this tool over laudus_list_stock or laudus_product_kardex, nor any exclusions or prerequisites. Usage is implied rather than stated.

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