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

Annotations already declare readOnlyHint=true, destructiveHint=false and idempotentHint=true, and the description reinforces this with the non-obvious statement that it 'opens nothing by itself' — resolving the tension between the 'create' name and a read-only operation. It also discloses why a browser-driven path is needed (no public API for leads, projects, estimates or invoices). It does not cover response size or whether instructions vary by account configuration.

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, and the operational content is front-loaded. However, 'Houzz Pro's official API: Houzz Pro has no public API...' repeats the subject awkwardly, and the dated verification stamp ('checked 11 Oct 2026') adds noise that could be compressed into a single clause.

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?

There is no output schema, so the description carries the burden of explaining returns, and it does: step-by-step screens, buttons and fields. It also supplies the downstream workflow and the rationale for not using an API. What is missing is any indication of how long or structured that returned guidance is, which matters for an agent planning its next call.

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 no per-parameter meaning to add and the baseline of 4 applies. The description does not pretend otherwise.

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 names the resource (estimate in the user's own Houzz Pro account) and immediately clarifies the actual output: step-by-step screens, buttons and fields, not a created record. The opening clause 'Create estimate...' reads as an action until the next sentence corrects it, so the reader must reconcile name against behavior, but the correction is explicit and adjacent.

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 a clear workflow: call this to get the procedure, then execute it with the cotlet_browser_* tools in the user's Houzz Pro Cloud Browser. That sequencing is actionable guidance an agent can follow without inference. It stops short of naming when not to use it (e.g., versus cotlet_app_guide or cotlet_apps for general app discovery).

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