search_houzz

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

No annotations are provided, so the description carries the burden of behavioral transparency. It describes the basic functionality (returns pro profiles) but does not disclose any potential behavioral traits such as rate limits, authentication requirements, or error handling. This is adequate for a simple search tool.

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, consisting of three short sentences that convey all essential information without any unnecessary words. It is well-structured and front-loaded with the main purpose.

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 simplicity and lack of output schema, the description adequately explains what the tool returns (pro profiles with ratings, reviews, projects, and contact info). It does not cover pagination, error handling, or performance limits, but it is sufficient for an agent to understand the tool's capability.

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 input schema has 100% description coverage for both parameters (url and limit). The description adds context by specifying that the url must be a Houzz search URL and that the tool returns pro profiles with specific details, which enhances understanding beyond the schema alone.

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 searches Houzz for home design professionals, contractors, and interior designers. It specifies the input (a Houzz search URL) and output (pro profiles with ratings, reviews, projects, and contact info), distinguishing it from sibling tools that search other domains.

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 tells the user to obtain a Houzz search URL by browsing houzz.com/professionals, providing clear guidance on how to prepare the input. It does not explicitly state when to use this tool versus alternatives, but the context is implicit given the sibling tools target different domains.

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