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

Annotations mark this as a write (readOnlyHint=false, non-idempotent), and the description adds genuinely useful context beyond them: PII is shared with a named third party, nothing is charged, and a new request returns a personal upload link while repeat requests may not. It stops short of stating rate limits or what an existing/duplicate request returns exactly.

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 tight sentences: what it requests, what to gather first, what it does not do, and what comes back. Front-loaded with the action and deliverable, with no 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?

With ten required-ish parameters, no output schema, and a third-party data handoff, the description covers both the intake requirements and the return shape. Minor gaps: it doesn't explain what happens if the person later adds photos/dimensions, or how the personal link expires.

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 description coverage is 100%, so all ten parameters (including units, ranges, and the consent constraint) are already documented. The description only re-mentions name, email, ZIP and consent in conversational terms, adding little format or semantic detail the schema lacks; 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?

States a specific verb and resource ('Ask ... for a Free Room Analysis') and defines the deliverable precisely: a recommended layout plus one written quote. The output description ('a personal link for adding photos, room dimensions or a short video') further separates it from the calculation/recommendation 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 explicit preconditions — collect first name, email, ZIP, and a clear yes to third-party sharing before calling — plus reassurance that nothing is ordered or charged. It does not name the sibling tools (e.g. asp_calculate_room_acoustics) or say when a public analysis request is the wrong path versus those alternatives.

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