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 useful context about result granularity (per receive item, lot/serial/track-by breakdown) but says nothing about permissions, result volume, or pagination behavior beyond what the schema documents.

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?

Three short sentences, front-loaded with scope before the identifier requirement and the endpoint. Nothing is padded, though the raw endpoint reference contributes little for an agent that already has the tool name.

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?

With no output schema, the description usefully characterizes the return shape as per-receive-item breakdown with lot/serial track-by values, and the schema fully covers parameters and paging. Only the absence of guidance versus the stock-summaries sibling leaves a real 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 coverage is 100% and the schema already documents all four parameters including pagination semantics and the facility_id source (extensiv_list_facilities). The description only restates that both ids are required, adding no meaning beyond the schema's required list.

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 resource and scope: all inventory for one customer in one facility, broken out by receive item with lot/serial track-by values. That is clearly distinct from order/carrier siblings, though it never names the closest alternative, extensiv_list_stock_summaries, so an agent must infer the detail-vs-summary split 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?

'Both ids are required' gives a prerequisite, but there is no explicit when-to-use or when-not-to-use guidance and no mention of extensiv_list_stock_summaries or extensiv_list_inventory as the alternatives for summary-level data. Usage is only implied by the described granularity.

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