search_properties

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

No annotations are provided, so the description carries full behavioral disclosure. It adds some context (e.g., location is fuzzy-matched, added_since formats, pagination via max_pages), but lacks details on rate limits, error handling, or result structure beyond parameter descriptions.

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 well-structured with a clear main sentence and an Args section. While lengthy due to 17 parameters, each line adds value because the schema lacks descriptions. The format is consistent and front-loaded.

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 17 parameters and no annotations, the description covers all parameters comprehensively, including validation hints. Output schema exists, so return format is not required. Lacks discussion of error cases or limit details, but is largely complete given complexity.

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 0%, so the description fully documents each parameter. It provides detailed explanations, valid value sources (e.g., get_facilities), format constraints (e.g., added_since), and defaults (e.g., max_pages=1), adding significant meaning 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?

The description clearly states 'Search for properties on Daft.ie with full filtering support', providing a specific verb (Search) and resource (properties). It distinguishes from sibling tools like get_facilities, which are helper functions for valid values.

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 referencing sibling tools within parameter explanations (e.g., use get_search_types() for valid search_type, use suggest_locations() for location). However, it does not explicitly state when not to use this tool or provide direct alternatives for similar tasks.

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