list_properties

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

With no annotations, the description must disclose behavioral traits. It does not mention that the tool is read-only, what the response contains (e.g., list of properties, count, pagination), or any side effects. It also fails to indicate that the tool requires multiple mandatory parameters or how errors are handled, leaving significant gaps.

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, front-loading the purpose in the first sentence and adding prerequisite and parameter guidance in the second. Every word is functional; no wasted space.

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 tool with 25 parameters (7 required) and no output schema, this description is too sparse. It omits crucial context: how to combine parameters for filtering, that operation is required, and what the output looks like. The agent would need to infer or guess many usage details.

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 100%, so baseline is 3. The description adds value by explaining that locationId, lat, lon come from the autocomplete endpoint and that propertyType can be set to specific values like Homes, Premises, etc. However, it does not elaborate on many other parameters (e.g., minPrice, operation), relying on weak schema descriptions.

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 states 'List Properties' as the action, identifies required parameters (locationId, lat, lon) and their source, and explains the propertyType parameter's role in filtering by property type. This differentiates it from sibling tools like get_suggestions (location autocomplete) and property_details (single property info).

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 instructs the agent to obtain locationId, lat, and lon from the autocomplete endpoint, providing a clear prerequisite. It also advises picking the propertyType for extraction. However, it lacks explicit guidance on when to use this tool vs. alternatives (e.g., when to call property_details instead) or situations to avoid.

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