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

With no annotations provided, the description fully carries the transparency burden. It proactively discloses privacy guarantees (no query, contact detail, identity, network address, referrer, or user-agent is disclosed) and cost implications (neither party charged; only downstream outcome can create a provider charge). It also clarifies that the handoff receipt is privacy-safe and that declining optional disclosure is non-blocking, providing comprehensive behavioral context.

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 five sentences, each adding distinct value: the core action, the receipt/return, the optional disclosure, the privacy scope, and the cost model. It is front-loaded with the primary purpose and contains no filler or redundant restatements of annotations.

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?

The tool has a complex consent workflow and no output schema, yet the description covers the main flow, return value (provider action URL), optional consent, privacy, and cost. It could additionally document failure modes or idempotency, but for a handoff continuation tool, the description adequately prepares an agent to invoke it correctly.

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 100%, so the baseline is 3. The description adds meaning by detailing exactly what the optional controlled-intent disclosure covers ('the ticket's controlled topic, region, USD budget band, urgency, and allowlisted requirement flags'), which is not specified in the schema's generic reference to a 'bounded controlled-intent bundle'. This helps the agent understand the semantic scope of the optional consent parameters.

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 clearly states the tool's function: 'Present the exact ticket bearer returned by prepare_provider_action', after which NHS records a handoff receipt and returns the attributed provider action URL. This specific verb+resource pairing distinguishes it from the sibling prepare_provider_action by referencing it as the source, making the tool's role in the workflow unambiguous.

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 description explicitly ties usage to the output of prepare_provider_action, implying the correct sequence. It also explains the optional controlled-intent disclosure and notes that declining it does not block the handoff, providing clear conditional usage. However, it does not explicitly exclude alternatives or describe when not to use the tool, only relying on the sequential dependency.

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