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

Annotations already declare readOnly, idempotent, non-destructive and non-open-world, so the safety profile is covered structurally. The description adds only the 'published' scope qualifier; it says nothing about result volume, ranking behavior, or error handling (e.g. the 400 on uncovered countries, which lives only in the schema).

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?

A single, front-loaded sentence with zero filler. It is efficient, though arguably too terse for an 8-parameter search tool with no exclusions or routing guidance.

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 complete schema docs and full annotations, no output schema, the minimum is met: the agent knows the resource, the facets, and the safety profile. Still missing is any usage framing (when this beats sibling lookups) and any hint of pagination/ranking in prose, leaving it merely adequate.

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% and each parameter is richly documented (slug sources, enum defaults, pagination protocol), so the schema carries the full burden. The description only restates the 'text, place and category' facets at a high level, adding no syntax or constraint detail beyond the schema.

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 (search) and resource (published agent wallets), plus the three query dimensions (text, place, category). This clearly separates it from get_listing (single fetch) and the list_* siblings, though it does not name any alternative explicitly.

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?

There is no when-to-use / when-not guidance and no mention of alternatives. The word "published" implies a scope restriction (not drafts), but the agent must infer that; nothing tells it when to prefer this over list_categories/list_places lookups or get_listing.

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