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

With no annotations, the description carries the full burden and does: it discloses that step 1 only validates and returns a summary/consent line/token, that nothing reaches providers until the person clicks an emailed link, that up to three installers are chosen by the calculator, and that the person can stop further disclosures. Mutation semantics, consent scope and downstream side effects are all covered.

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?

Front-loaded with the purpose and the two-step flow before the long consent block, and every sentence about the protocol earns its place. The full verbatim consent text is repeated from the schema's consent description, which is the one clearly redundant element.

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?

No output schema exists, so the description must explain returns — and it does: step 1 returns a summary, the consent line and a confirmation token, and step 2 triggers an email with a verification link before providers see anything. For a nested-object, multi-call mutation tool, an agent has everything it needs.

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% so the baseline is 3, but the description adds real sequencing semantics the schema cannot express: 'answers' are keyed by field key from enquiry_fields, consent=true is required in both steps, and 'confirmation' is only supplied on the second call after approval. That is meaningfully more than the field-level descriptions.

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?

States a specific verb and resource (submits an enquiry to California Solar Cost Calculator) and immediately draws the boundary against adjacent concepts: NOT a purchase, NOT a guaranteed quote. It also names enquiry_fields as the source of the answer keys, which orients the agent among its siblings.

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?

Gives an explicit two-step protocol with the gating condition spelled out: step 1 call with answers plus consent=true, and step 2 'only if the person agrees' with the same answers plus the confirmation token. When to call, when to call again, and what must happen in between are all unambiguous.

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