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

Annotations only declare readOnlyHint=false, openWorldHint=true, idempotentHint=false and destructiveHint=false; the description adds substantial context beyond that — outreach channels (email, SMS, phone), human operator involvement, an approximate one-hour target for urgent requests with explicit non-guarantees, and the key behavioral fact that this creates a request rather than a confirmed booking, with the customer paying the provider directly.

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?

It is front-loaded with the trigger condition and well organized, but it is a single dense paragraph and the enumerated trade list largely duplicates the trade enum already present in the schema, which is mild redundancy in an otherwise efficient description.

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 15-parameter, open-world tool with an output schema, the description covers the essentials an agent cannot infer: consent collection, outreach mechanics, timing expectations and their limits, and the fact that no appointment is confirmed. Return-value detail is correctly left to the output schema.

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 67% across 15 parameters, and the description adds essentially no per-field meaning beyond instructing the agent to collect all required fields and explicit consent. The consent emphasis is useful, but the remaining parameters rely on the schema, so this sits at the moderate-coverage baseline.

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 trigger-and-action: 'Use when a customer wants an agent to find and book a home-service contractor,' and then names the concrete resource created ('This call creates a service request'). It also draws the boundary that separates it from the read-oriented siblings get_coverage and get_request_status by stating it does not confirm an appointment or authorize work.

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 'Use when...' clause gives an explicit, unambiguous condition for invoking the tool, and the closing sentence adds a prerequisite ('Collect every required field from the customer first, including explicit consent'). It does not, however, name or route to alternative tools, so it falls short of the 5-level when/when-not/alternatives standard.

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