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

Beyond the readOnlyHint annotation, the description discloses important runtime behavior: bookings are scoped to the current team, results are returned earliest-first, attendee name/email are masked, and pending status depends on requireApproval. The mention of masking and the approval model is genuinely valuable and not visible from the schema.

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 compact and well organized: what is listed, what fields come back, what filters exist, a typical use, and a key PII mask. Every sentence earns its place, with no filler or restating of the tool name.

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 read-only listing tool with nine optional parameters, the description covers the payload shape, filtering semantics, sorting, a pragmatic example, and the data masking behavior. Combining this with a complete schema and output schema leaves almost no open questions for invoking the tool 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 solid, but the description adds real semantic value: it maps formId to quiz, recordId to submission record, and clarifies that examineeId is the internal id from get_lead's respondent.id, not the business code. It also explains what status 'pending' means in context.

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 specific verb ('List') plus a clearly bounded resource: '1:1 bookings of the current team.' It gives the booking origin, the sort order, and what each item contains, which unambiguously distinguishes it from siblings like reschedule_booking, review_booking, or update_booking_status.

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 gives a concrete use case ('status "pending" lists the approval queue') and explains when requester approval applies. It does not explicitly contrast against alternative booking-related tools, but the context is clear enough for an agent to know this is the read-side listing tool.

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