ListingsItems_searchListingsItems

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

With no annotations, the description carries the full burden of behavioral disclosure. It mentions the execution environment and states it returns a list, but it does not disclose authentication needs, rate limits, pagination behavior, read-only guarantees, or any side effects.

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 short and mostly purposeful, with the environment caveat front-loaded. The phrase 'Catalog entry' adds only marginal value, but overall the text is compact and not padded.

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?

The description does not provide enough for an agent to invoke the tool confidently: there is no output schema, no parameter guidance, and no behavioral context beyond returning a list. For a search operation, essential details like search criteria, result structure, and constraints are missing.

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 schema declares zero parameters, so there are no parameter semantics for the description to add beyond the schema. The baseline for a zero-parameter tool is appropriate here, though the loose additionalProperties:true means actual accepted inputs remain ambiguous.

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 clearly identifies the operation as searching for and returning a list of selling partner listings items with their details. It is distinct enough from get/put/patch/delete siblings, though it does not explicitly differentiate itself from them.

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?

The description gives no explicit guidance about when to use this tool versus sibling tools like ListingsItems_getListingsItem. The phrase 'Runs in your Kuudo deployment, not here' hints at an environment constraint but does not clarify when an agent should select this tool or what alternatives exist.

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