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 externally. The description adds the HTTP endpoint (GET /items) and the returned field list, which is modest extra context, but it discloses nothing about pagination limits, rate limits, or result size — and with openWorldHint=true, some note on external data variability would help.

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?

Two short fragments, front-loaded with the resource identity, with zero filler. It is arguably clipped to the point of under-specification, but nothing in it is wasted.

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 7 optional parameters and no output schema, the description should carry more weight: it hints at the response shape via the field list but omits the pagination contract (next_page, per_page defaults) and does not clarify that all parameters are optional filters. Serviceable but leaves clear gaps an agent must fill from the schema alone.

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 the baseline is 3; the description goes slightly beyond by naming the catalogue attributes (name, price, currency, unit, tags) that the filtering and sorting parameters operate over, helping the agent infer useful values for search, order_by and tag_name. It still does not explain page/per_page interplay.

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 identifies the resource as a product/service catalogue and lists the fields it exposes, which tells the agent what kind of data comes back. However, it never uses a verb like "list" or states scope (all items vs. filtered), and it says nothing to distinguish it from sibling invbg_get_item or invbg_create_item beyond the plural noun.

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 on when to use this tool versus invbg_get_item (single record) or invbg_list_item_units, nor any mention of pagination workflow such as following next_page. The only usage hint lives in the schema's parameter descriptions, not the tool description.

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