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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds two useful behavioral facts: results are restricted to published listings, and paging is offset-based. It does not disclose sort order, what an out-of-range offset yields, or whether any total count is returned.

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, filter capability front-loaded and pagination noted second. No redundant restatement of the title and no filler.

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 five-parameter, fully-optional search with no output schema, the definition covers what it filters on but leaves the result shape and default ordering unexplained. Since no output schema exists, an agent cannot learn from structured fields what a listing record or page envelope looks like, which is a real gap for a search tool.

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 description coverage is 100%, so every parameter is already documented, including the 'next_offset from the previous page' hint for offset. The description only restates the filter dimensions at a higher level and adds no syntax or edge-case detail beyond the schema; 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 published listings') plus the filter dimensions (category slug, city, name fragment), and the 'published' qualifier narrows scope meaningfully. It does not explicitly contrast with sibling reads like get_listing, but search-vs-fetch is unambiguous.

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 'and/or' phrasing implies filters can be combined or omitted, and mentions pagination, so the usage pattern is inferable. However, there is no stated when-not guidance, no note on what happens with zero filters, and no routing toward list_categories (needed to obtain slugs) or get_listing for single-record fetches.

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