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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false; the description reinforces this with 'opens nothing by itself', which is genuinely useful for an agent worried about unintended side effects. It also discloses the return content (screens, buttons, fields). It omits any mention of auth/prerequisite state in the user's Houzz Pro account, which is the main remaining gap.

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?

Three sentences, front-loaded with the action and immediately followed by the caveat about what it actually returns. The final sentence on the missing official API is relevant context but phrased as a slightly awkward fragment ('Houzz Pro's official API: Houzz Pro has no public API...'), and the ChatGPT/Claude/any-AI-agent clause is filler.

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?

For a zero-parameter, read-only guidance tool with no output schema, the definition covers what it returns and what the agent should do next. Nothing critical is missing, though noting the prerequisite (an authenticated Houzz Pro session in the Cloud Browser) would close the last gap.

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 tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline applies. The description does not need to compensate for any schema gap.

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 states a specific verb and resource ('Update lead status in the user's own Houzz Pro account') and immediately clarifies the actual behavior: it returns step-by-step instructions rather than performing the change. That distinction sets it apart from action-style siblings like houzz_pro_send_invoice. It loses a point only because the name/title imply an action the tool does not itself take, which the agent must resolve from sentence two.

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?

It gives an explicit workflow hand-off: after reading the steps, perform them with the cotlet_browser_* tools in the Houzz Pro Cloud Browser. It does not name a when-not case or an alternative guidance tool, so the routing guidance is clear but not exhaustive.

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