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

Annotations already declare read-only/idempotent behaviorpin, and the description adds valuable operational traits: pagination must use the returned nextCursor with unchanged filters, and ambiguous locations must be resolved first. This goes beyond the structured safety hints and describes how to interact correctly.

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?

Three sentences, front-loaded with the primary use case, followed by compact, actionable guidance on location resolution and pagination. No redundancy or 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?

The description covers main usage triggers and pagination, but omits parameter semantics, filter combination logic, and guidance on choosing among location filter types. The output schema exists, yet the operational context for a complex search tool is only partially provided.

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 4%, leaving 26 parameters undocumented. The description references broad categories ('location, budget, rooms or amenities') but does not explain the meaning or interaction of specific filters such as bbox, radius, polygon, or how filters combine. This is insufficient for a 27-parameter tool.

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?

The description clearly identifies the tool as a search for public properties with specific filter dimensions (location, budget, rooms, amenities). It distinguishes itself from siblings like get_property_by_slug (single property) and compare_properties by being the general listing search.

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?

It explicitly states when to use the tool ('Use this when the user wants public properties by location, budget, rooms or amenities') and gives operational guidance (resolve ambiguous locations, use explicit filters, maintain cursor). However, it does not name alternatives or provide when-not-to-use exclusions, so it misses the highest bar.

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