search_catalog

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

No annotations are provided, so the description carries the burden; it conveys that this is a read-only search that returns a compact paginated list with named fields. It omits explicit read-only confirmation, auth requirements, and rate-limit behavior, but the operational profile is otherwise clear.

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?

Front-loads purpose, then workflow, then return shape. The catalog/marketing context earns its place by motivating use, though the buy-box/traffic aside is slightly verbose for a tool definition.

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 steps up by describing the return ('product id, name, thumbnail and main attributes, paginated'), and it names the two follow-on tools an agent needs. Nothing essential for correct invocation is 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?

Schema coverage is 100%, so the schema already documents query, limit, and offset. The description's 'paginated with limit/offset' merely restates the schema and adds no format or constraint detail beyond it; baseline 3 applies.

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 ('Search Mercado Livre's product catalog') and immediately clarifies what a catalog product is. It distinguishes this catalog-specific search from generic product search and names the downstream tools (get_catalog_product, create_catalog_listing).

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?

Explicitly states the purpose of use ('find the catalog_product_id for a product you sell') and the sequencing ('then inspect it with get_catalog_product and link your listing with create_catalog_listing'). The agent knows exactly when to reach for this and what follows.

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