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

Annotations already mark this as a non-read-only, open-world, non-idempotent write, and the description goes well beyond them by disclosing cost (free to the homeowner), latency (callback within the hour during business hours), and the return shape (a reference plus next steps). It also flags the consent prerequisite, which is the key behavioral constraint on a real-person callback booking and is not encoded in any structured field.

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 core information is front-loaded and the closing pointer to check_service_area is well placed, but the callback detail is duplicated in a redundant parenthetical ('A vetted local pro calls them back (a vetted local pro calls back within the hour during business hours)'). That repetition costs space without adding information and makes the sentence read as unedited.

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?

For a 7-parameter mutation with no output schema, the description covers the essentials an agent needs: eligibility and consent, cost, response time, what is returned, and where to verify coverage. It does not state what happens on failure (e.g. out-of-area ZIP rejection or a bad phone number), which is the main remaining gap.

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 every parameter is already documented with type, bounds, and examples (e.g. 'need' examples, phone format). The description adds only indirect meaning, such as the North Jersey ZIP constraint and the consent/real-person framing, rather than explaining individual fields. Baseline 3 is appropriate when the schema carries the parameter burden.

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 opens with a specific verb and resource ('Book landscaping') plus a tight geographic and eligibility scope ('North Jersey area', 'a real person who asked for it, with their consent'). That distinguishes it immediately from check_service_area (area validation) and get_service_info (informational lookup), so an agent can route correctly without opening the schema.

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 condition for use (a person who asked for it and consented) and explicitly names the sibling to call first when coverage is uncertain: 'Check the ZIP with check_service_area first if unsure.' There is no explicit when-not-to-use guidance for the remaining sibling or for cases where the request is out of area rather than merely uncertain, so it stops short of a full routing spec.

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