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

With no annotations, the description carries the full behavioral burden and does meaningful work: it discloses the default availability filter, the stock-ordering priority (AutoID stock before distribution-only stock), and the shape of returned commercial cards including pricing fields. It omits pagination behavior and truncation semantics for limit/offset.

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 compact sentences with the core purpose and default filter front-loaded, then the availability rule, then return details. Every sentence conveys information; there is no filler or restatement of the 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 read-only list tool with no output schema, the description supplies the default scoping, ordering behavior, and the shape of returned card pricing, which is the right level of detail. Minor gaps remain around pagination and the non-default availability enum values, but an agent can invoke it correctly from this.

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 only 25% (only 'model' is documented), so the description must compensate. It adds useful semantics for availability (default value and the specific condition for 'all'), but says nothing about limit, offset, or the meaning of the autoid/supplier/out_of_stock enum values, leaving half the parameters unexplained.

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 ('Lists exact SKUs belonging to an AutoID grouped product'), which is clearly distinct from generic product search or group-fetch siblings. It scopes the operation to AutoID grouped products, though it does not explicitly name the sibling tool (get_product_group) an agent might confuse it with.

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?

Gives an explicit when-to-use rule for the availability parameter: use availability=all 'only when the user explicitly needs unavailable configurations too,' and states the default is available. No alternative tools are named and no prerequisites are stated, so it falls short of full routing guidance.

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