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

Annotations already declare non-readOnly, non-destructive, non-idempotent and open-world, so the safety profile is covered. The description adds genuinely useful context beyond that: the call returns a draft (with total or estimate, windows, ref, customer_token) and nothing is committed to the business until approve_request is called.

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?

A single dense paragraph that front-loads the core purpose ('One call for any trade job') then lists inputs and return behavior. It is information-rich with little waste, though the run-on parameter enumeration is somewhat heavy.

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 an 11-parameter, nested-object tool with no output schema, the description does explain return shape and the draft/approve lifecycle, which is valuable. But it omits the required 'slug' parameter and several optional inputs, so an agent cannot fully assemble a valid call from the description alone.

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 55% and 11 parameters exist, so the description carries meaningful burden. It explains service_sku vs description matching, intake_answers field ids, customer, preferred_time and slot_start, but never mentions the required 'slug' parameter nor notes, photos, urgency or referred_by, leaving key inputs undocumented.

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 (place) and resource (service request) and scopes it as 'one call for any trade job (repair, quote, booking)', which helps distinguish it from narrower siblings like request_quote and book_slot. It does not fully differentiate from place_order, but the trade-service framing is clear.

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?

Implied usage is conveyed through cross-references ('intake_answers keyed by the field ids from get_service_requirements', 'slot_start when the flow is book_then_pay', 'Nothing reaches the business until approve_request'), which sketches the workflow. However, it never explicitly says when to choose this over the sibling alternatives place_order or request_quote.

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