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

The annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, and the description reinforces rather than contradicts them by stating it 'opens nothing by itself'. It adds real context beyond the annotations: the return format (screens, buttons, fields) and the dependency on the user's own Houzz Pro Cloud Browser session. It does not cover auth prerequisites or what happens when the session is missing.

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 core correction that this tool returns instructions rather than performing the send. The trailing note about Houzz Pro having no public API justifies why a browser step is required, but it is dated trivia that only marginally earns its place.

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?

With no output schema, the description carries the burden of describing the return value and does so concretely ('step by step (screens, buttons, fields)'). Combined with rich annotations, an agent has enough to call it correctly; only edge cases such as a missing browser session or signed-out account are left unexplained.

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 parameter semantics to explain and the baseline is 4. The description adds nothing spurious about inputs and correctly implies the call needs no arguments.

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 a specific resource (Houzz Pro invoice) and, crucially, corrects the misleading name by stating it 'Returns how to do it in Houzz Pro step by step' and 'opens nothing by itself'. That makes the actual function distinguishable from the sibling houzz_pro_create_* tools. It stops short of a 5 because the opening sentence ('Send invoice in the user's own Houzz Pro account') can still be read as a write action until the second sentence clarifies.

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 explicit routing: use this to get the steps, then 'do it with the cotlet_browser_* tools in the user's Houzz Pro Cloud Browser', which points to the correct alternative tool family. It does not state any when-not-to-use condition (e.g., if the user has no Cloud Browser session or no Houzz Pro account), so it falls short of a 5.

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