Use when the user is ready to submit details for a real TaskMan of London booking request.
| Name | Required | Description | Default |
|---|---|---|---|
| No | |||
| phone | Yes | ||
| source | No | chatgpt_app | |
| postcode | Yes | ||
| photos_url | No | ||
| service_type | Yes | ||
| task_summary | Yes | ||
| customer_name | Yes | ||
| preferred_date | No | ||
| idempotency_key | No | ||
| time_preference | No | ||
| consent_to_contact | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full burden. It only says 'real' to imply this is a committed booking, but omits side effects, whether confirmation is required, idempotency behavior, or any other behavioral traits an agent would need to anticipate.
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 description is a single short sentence, which is efficient, but it is under-specified rather than concise. It lacks essential detail, so it does not earn a high score for structure.
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?
Given the complexity (12 parameters, no output schema, no annotations), the description is severely incomplete. It does not explain what a booking request entails, what 'real' means in workflow, or any post-call expectations.
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 0% and the description adds no parameter meanings. With 12 parameters, the agent receives no guidance beyond raw names, types, and enums, which is insufficient for confident invocation.
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 implies a specific action: submitting details for a real TaskMan of London booking request. It identifies the resource and the intent clearly enough, though it does not explicitly distinguish from the sibling tool create_customer_booking.
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 provides a clear trigger condition ('when the user is ready') and hints at the context (real booking request). However, it does not mention exclusions or alternative tools, so it loses a point for lack of explicit when-not-to-use guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Some tools overlap in purpose, such as check_availability vs get_customer_availability and the various verification entry points. Descriptions clarify the context of each, but an agent could still misselect without careful reading.
All tools follow a consistent verb_noun pattern with snake_case, e.g., check_availability, create_booking_request, get_booking_status. This makes the naming predictable and easy to navigate.
With 20 tools, the server is on the heavier side but the scope is broad, covering booking, customer verification, payments, and provider matching. The count feels slightly high but each tool serves a distinct step in the workflow.
The tool surface covers the full booking lifecycle from availability and quote to payment and final creation. Notable gaps include lack of update or cancel booking operations, but the core flow is well covered.