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

With no annotations, the description carries the full burden. It does disclose two useful traits: results are limited to 'active' listings (excludes inactive/sold) and prices are denominated in EUR. However, it says nothing about result ordering, pagination/default limit, or auth requirements, which matter for a search tool.

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 short sentences, front-loaded with what is searched, no filler. It is efficient but also under-specified, so brevity here trades off against completeness rather than reflecting tight polish.

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?

A 5-parameter search tool with no annotations and no output schema needs the description to explain filtering behavior, pagination, and at least a hint of the result shape. Apart from the 'active' filter and EUR currency, almost nothing an agent needs to call this correctly is covered.

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 only 20% — just the `query` parameter has a description. The description adds only the EUR unit for max_price_eur/min_price_eur, leaving `limit` (default, max 50), `category` enum intent, and the semantics of combining filters undocumented in both schema and description.

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?

Names a specific verb (Search) and resource (active Kiosq listings) plus the domain of items covered (agents, bots, prompts, models, SaaS, startups). It is clearly distinct from get_listing and publish_listing, though it does not explicitly state the differentiator.

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 purpose implies browsing before buy_listing/get_listing, but there is no explicit when-to-use, no mention of when to prefer get_listing for a single known listing, and no guidance on combining query with category or price bounds. Usage is inferred from the name and sibling set only.

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