firestarter_catalog_search

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

Although annotations declare readOnlyHint=true, the description meaningfully extends beyond that: it discloses result contents (listing id, share link, buyable flag), explains buyable vs browse-only semantics, and describes ordering (buyable, cheapest first) and limit behavior. It reinforces the read-only nature with 'never charges or changes anything', which adds trust and clarity.

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 moderately long but every sentence contributes: purpose, differentiation, result contents, ordering, country, limit, and safety. It is well-structured and front-loaded with the core purpose, making it efficient to parse.

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?

Given the tool has 7 optional parameters, no output schema, and a nontrivial search/ordering/limit behavior, the description covers all essential aspects: what results include, how to buy, buyable/browse-only distinction, country filtering, limit behavior, and read-only guarantees. It is sufficiently complete for an agent to invoke correctly without further documentation.

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 baseline is 3. The description adds value by explaining the consequence of exceeding the limit (result notes when more exist) and advising the user to narrow the query or raise limit. It also contextualizes country usage for shipping filters, which is partially redundant with the schema but adds a user-oriented framing.

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 uses a specific verb (Search) and resource (Firestarter NETWORK catalog), and clearly scopes it to ALL sellers and buyer-facing browsing. It explicitly distinguishes from firestarter_listings, which shows only your own seller listings, making the tool's purpose unmistakable.

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 states concrete use cases (see what's available before buying, compare prices, check network availability) and explicitly contrasts with firestarter_listings as the seller-listing alternative. It also provides cross-tool guidance by mentioning that the returned listing_id can be passed to firestarter_execute to buy.

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