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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is fully covered. The description adds one genuinely useful behavioral fact – only 'published' homes are returned – but says nothing about pagination behavior, empty-result handling, or result ordering beyond what the schema states.

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 no filler; the verb, resource, scope qualifier ('published'), and filter axes all land in the first clause. Nothing redundant or trailing.

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 8 parameters, 0 required, and no output schema, the description leaves real gaps: no statement of what a response contains, how `cursor`/`limit` paginate, or how multiple filters combine (AND semantics). The 'published' scoping helps, but an agent still has to infer the result envelope from the cursor parameter description.

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 parameters are already well documented (q semantics, slug formats, sort defaults, opaque cursor). The description only restates the filter axes at a high level and adds no syntax, format, or interaction 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 (Search) and a well-scoped resource (published memory care homes) plus the three filter axes. An agent can tell it apart from get_listing (single record) and the list_* siblings, but the description never names or contrasts those alternatives 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-to-use, or alternative-tool guidance. Nothing tells the agent when to prefer search_listings over get_listing, list_places, or list_categories, or that a bare browse without `q` is also valid here. Usage is only weakly implied by the facet list.

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