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 that the returned figures fold in open sales orders, purchase orders and work orders, which is genuine output semantics, but it says nothing about pagination or rate behavior (that lives only in the schema).

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 resource and returned fields are front-loaded in a single dense sentence, followed by filtering capabilities and the endpoint. Efficient, though the opening sentence is heavily comma-laden and could have been split for scannability.

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 enumerates the fields returned, which is exactly what an agent needs to know what comes back. Filtering options and the location-id cross-reference are covered between description and schema; only paging/limit behavior is left entirely to the schema.

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 100%, so all 11 parameters — including limit's no-page-offset rule and the filters array semantics — are already documented in the schema. The description only restates the filter categories at a high level and adds no syntax or format detail beyond that, hitting the baseline for full schema coverage.

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 names the exact resource (stock per product per inventory location) and enumerates the returned quantities — physical stock, on hand, on hold, not-yet-shipped, not-yet-received and alert level. An agent can distinguish this from sibling list tools such as megaventory_list_products without opening the 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?

It lists the available filtering axes (product ids, SKU, category, location, supplier, below alert level), which implies how the tool is meant to be narrowed, and the schema cross-references megaventory_list_inventory_locations for valid location ids. However, there is no explicit when-to-use vs when-not (e.g. versus list_products or get_product_bom), so usage must be inferred.

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