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

No annotations are provided, so the description carries full burden. It discloses the tool searches and returns links, but does not mention behavior like pagination, error handling, rate limits, or any destructive aspects. This is adequate for a straightforward search tool but lacks depth.

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?

The description is two sentences long, front-loading the primary purpose and returning value. Every sentence adds essential information without redundancy.

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?

Given 11 parameters, no output schema, and no annotations, the description covers the core functionality but omits details on result ordering, pagination, or multi-city search limits. It is adequate for basic use but leaves some behavioral aspects undefined.

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?

With 91% schema coverage, the description adds meaning beyond the schema by explaining the context of parameters (e.g., maxPrice meaning differs for rent vs sale, property categories like 'stan' for apartment). It does not simply repeat schema definitions.

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?

Description clearly states it searches property listings for rent or sale in Croatia, specifying the property types (apartments, houses, land, commercial) and that it returns links to trazimstan.hr. This distinctively sets it apart from sibling tools like 'get_listing' or 'get_price_stats'.

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 description implicitly guides usage by stating the tool's purpose and scope (Croatian real estate ads for rent or sale). While it does not explicitly state when not to use it or point to alternatives, the context of siblings makes it clear that this is the appropriate tool for property searches.

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