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

Annotations already declare the safety profile (write, non-destructive, open-world), so the bar is lower, and the description adds real context beyond them: it discloses the Cotlet API key/auth requirement, notes the lead is correctable by hand if wrong, and constrains lead_source to entries in the Lead Sources list. The phrasing is garbled but the behavioral information is substantive.

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 first two sentences ("Houzz Pro: New lead in your pipeline. Adds a lead to your pipeline.") are redundant restatements of the title. The clause "The lead reaches no client and is fixed by hand if wrong, so this tool runs without asking" is awkward and buries the useful no-confirmation point, though later sentences are reasonably economical.

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 11 params at 100% schema coverage, no output schema, and annotations present, the description is adequately complete: it names required fields, discloses auth requirements, and constrains the source field. Only the opaque "reaches no client" phrasing leaves a minor gap in what the created lead's state actually is.

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?

Schema coverage is 100% across all 11 parameters, so the schema carries the parameter semantics. The description only restates the required/optional split and adds the Lead Sources constraint on lead_source, which is marginal added meaning over the schema's "Where the lead came from." Baseline 3 applies.

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?

"Adds a lead to your pipeline" gives a specific verb+resource that clearly identifies creation. It doesn't explicitly contrast with the sibling lead tools (convert_lead_to_project, get_lead, list_leads, update_lead_stage), so differentiation is left to the name.

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 states requirements (lead_name and client_name required, everything else optional) and that the tool "runs without asking," implying no confirmation is needed. It gives no explicit when-to-use vs. when-to-use-an-alternative guidance, so usage is only implied.

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