Search Glongus listings

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

With no annotations provided, the description carries the burden of behavior disclosure. It adds useful context: no auth needed, prices are in pence (2500 = £25.00), and returns listings plus total count. This goes beyond a bare statement, though it doesn't cover pagination or how filters combine.

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?

Two sentences, front-loaded with the core purpose, and every clause adds information (marketplace, active, GBP, pence, auth, return count). No redundancy or fluff.

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 search tool with no output schema, the description covers the essential aspects: what is searched, currency and price unit, auth expectations, and return shape (listings + count). It omits behavior such as default sorting or filter combination logic, but given the simplicity and high schema coverage, it is reasonably complete.

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 baseline is 3. The description adds value by clarifying the price unit (pence) directly relevant to max_price_cents, and specifying that search covers title and description (via schema). This extra context pushes it to 4.

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?

Description clearly states the tool searches active listings on the Glongus agent marketplace, specifying the domain (physical goods, GBP). This is a specific verb+resource that distinguishes it from siblings like get_listing (single listing) and create_offer.

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 implies usage for searching listings but does not explicitly contrast with alternatives like get_listing. It mentions 'active listings' and 'No auth needed' which gives some context, but lacks explicit when-to-use or when-not-to-use guidance.

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