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

Annotations declare the safety profile (readOnlyHint=false, idempotentHint=false, destructiveHint=false, openWorldHint=true), so the bar is lower, yet the description adds real side-effect detail: emails the booking to legal@unifiedchambers.com with a copy to the Senior Partner's mailbox plus an acknowledgement to the user. It does not address duplicate-submission behavior, which matters for a non-idempotent write tool.

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?

Two sentences, no filler. The precondition ('after the user has paid') and the core payload are front-loaded, and the side-effect and scope-disclaimer clauses follow in the order an agent needs them.

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 10-parameter, 8-required non-idempotent write with no output schema, the description covers the flow, the precondition, and the downstream emails adequately. It is silent on failure/duplicate handling and on what the caller receives back, which is a minor gap given no output schema exists.

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, both enums, and the slot format are already documented in the schema. The description lists the same fields but adds no format, constraint, or validation meaning beyond it, so the baseline of 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 — records a consultation booking — and enumerates exactly what the booking consists of (name, phone, matter type, summary, UTR, preferred date/slot). The closing line 'Does not make or verify any payment' cleanly separates it from the sibling payment tool, so an agent can route between them without opening either 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?

Gives a clear precondition: this is used only after the user has paid the fee from their own bank app. The negative clause 'Does not make or verify any payment' functions as a when-not. However, no sibling is named explicitly (e.g. consultation_payment_details for collecting the fee), so the routing is inferred rather than stated.

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