search_by_profile

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

No annotations are provided, so the description carries the full burden. It discloses the use of hard filters and vector search, and explains the hours=0 behavior. It does not explicitly state if the tool is read-only, but the action 'Show' implies no side effects.

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 extremely concise with two sentences plus a note, all front-loaded with the main purpose. Every sentence adds value with no 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 the tool's complexity (semantic search with profile), the description explains the core logic and key parameter behavior. The presence of an output schema covers return values, so completeness is high. A minor gap is the lack of explanation for the limit parameter.

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 schema has 3 parameters with 0% description coverage. The description provides meaningful context for hours (explaining the special value 0 disables time filter), but does not explain limit or profile_id beyond their roles as inputs. Baseline is 3 due to lack of schema descriptions, and the description partially compensates.

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 tool shows apartments matching a search profile, ranked by semantic similarity. It distinguishes itself from sibling tools like search_apartments and semantic_search by specifying it uses a profile's hard filters and nl_description.

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 clear context on when to use this tool (when you have a profile) and gives a specific tip about hours=0. However, it does not explicitly state when not to use it or mention alternatives, though the sibling list implies differentiation.

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