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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description reinforces this with 'Nothing here sends anything,' then adds substantial non-obvious behavior: which cohorts get dropped and counted in `excluded`, that `nextAction` flips from nudge to close when nudges run out, and that the send tools re-check every rule and refuse in words. This is meaningfully more than the annotations convey.

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 one-line definition of the population, then structured into row-field, exclusion, and action paragraphs where each sentence carries information. It is dense and long, but nearly every clause earns its place; only marginal tightening is possible.

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?

With no output schema, the description enumerates the returned row fields (name, company, bookingLinkSentAt, nextAction, thread, etc.) and explains their meaning, the exclusion accounting, and the follow-up tools. For a five-parameter read tool with annotations covering safety, nothing an agent needs to call it correctly is missing.

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 five parameters (limit, sessionId, sessionLabel, sessionLabels, threadMessages) are already documented in the schema with defaults and bounds. The description adds field-level meaning via the `thread` / bookingLinkSentAt explanation, but says nothing about selector or limit semantics beyond what the schema provides, so the baseline 3 is correct.

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 states a precise population and scope: people who AGREED to a call, have not booked, and whose check date has arrived — the worklist for a booking routine. It explicitly distinguishes itself from li_replies_to_answer (those who wrote back) and from the case of someone only sent the link who never agreed, so an agent can separate it from siblings like li_bookings without opening a 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?

It routes the agent concretely: nudge via li_send_reply(bookingNudge: true) and close via li_send_reply(bookingClose: true), and points the excluded cohort at li_replies_to_answer. It doesn't phrase an explicit 'use this when X, not Y' rule, but the worklist framing plus named alternatives supplies clear usage context.

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