semantic_search

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

No annotations are provided, so the description carries full burden. It states the use of semantic/vector search but does not disclose key behaviors such as result ranking, pagination, error handling, or whether queries are case-sensitive. The description is minimal and leaves behavior largely inferred.

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 short and front-loaded with purpose, followed by examples and available filters. It avoids redundancy but could be slightly more structured (e.g., separate sections). No wasted words.

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 5 parameters, 0% schema coverage, no annotations, and an output schema (not shown), the description is too brief. It does not clarify what the output contains or how results are returned. For a semantic search tool, missing details like relevance scores or result format limit completeness.

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 0%, so description must compensate. It mentions optional filters (city, max price, room count) and provides examples, but does not explain the 'n_results' parameter or the exact format of filter values. The examples add some value beyond the schema, but for 5 parameters, more detail is needed.

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 resource ('apartments'), specifies the method ('semantic/vector search'), and distinguishes from sibling tools like 'search_apartments' (likely keyword-based) and 'search_by_profile'. Examples illustrate the type of queries supported, making the purpose unambiguous.

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 provides examples and mentions optional filters, but does not explicitly guide when to use this tool versus alternatives (e.g., keyword-based search or profile-based search). It implies use for natural language queries but lacks explicit context or exclusions.

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