ProductPricing_getListingOffers

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

There are no annotations, so the description must carry the transparency burden. It does disclose an execution trait ('Runs in your Kuudo deployment, not here') and says the tool 'returns' data, implying read-only behavior, but it does not mention side effects, auth requirements, rate limits, or response behavior.

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 description is only three short sentences with little waste. However, the most action-relevant purpose is placed after the 'Catalog entry' and environment warnings, so it is not optimally front-loaded.

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 simple, no-schema read tool, it provides the core purpose and an important environment caveat. It is incomplete around return format, error/pagination behavior, and what 'not here' means operationally, and there is no output schema or annotation to fill that 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?

The input schema has zero declared properties, so the 0-parameter baseline is 4; the description nevertheless adds meaning by specifying the scope is a single SKU listing. It still does not name a concrete parameter key, but that is an acceptable gap given the empty schema.

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 states a specific action ('Returns the lowest priced offers') on a specific resource ('a single SKU listing'), so an agent can recognize the core purpose. It does not explicitly contrast with sibling tools like getItemOffers or getListingOffersBatch, and the 'Catalog entry... not here' preamble adds slight ambiguity, which keeps it below a 5.

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?

Usage is implied: use when you need lowest-priced offer data for one SKU listing. The line 'Runs in your Kuudo deployment, not here' gives an environment constraint, but no sibling alternatives or when-not-to-use conditions are named.

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