plu_search_homes

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

The description does not disclose any behavioral traits such as authentication requirements, rate limits, or side effects. With no annotations to provide safety hints, the description leaves the agent unaware of essential behavioral context.

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 very concise at only three words, but it lacks structure. While it avoids verbosity, it is too brief to convey necessary information, balancing conciseness with adequacy.

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 the tool's 6 parameters, no output schema, and no annotations, the description is critically incomplete. It does not explain pagination behavior, return format, filter semantics, or required parameters, making it insufficient for reliable agent invocation.

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?

The description adds no meaning beyond the input schema, which itself has 0% coverage (no parameter descriptions). Parameters like 'location', 'country', 'startDate' are named but their roles, formats, or constraints are not explained, forcing the agent to infer.

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 the verb 'search' and the resource 'homes', indicating a search capability. However, it does not differentiate from sibling tools like 'plu_quick_search' or 'plu_get_my_properties', which may also involve searching or listing properties.

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?

No guidance is provided on when to use this tool versus alternatives. There is no mention of prerequisites, appropriate contexts, or scenarios where this tool is preferred over siblings such as 'plu_quick_search' or 'plu_get_exchanges'.

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