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

Annotations already declare readOnlyHint/idempotentHint, but the description adds the non-obvious rationale — appointments are never hand-inserted or edited over this server, so write tools are absent by design. That prevents an agent from hunting for a create/update sibling. Pagination and ordering behavior are not disclosed.

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?

Three short sentences: resource definition first, read-only constraint second, sibling routing last. No filler, and the most decision-relevant constraint is front-loaded after the resource statement.

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?

There is no output schema, so the description carries some burden for return shape — it doesn't say whether results are paginated envelopes, what fields appear, or default ordering. For an all-optional-filter list tool the scope statement is enough to call it correctly, but not enough to interpret results.

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 four parameters (page, leadId, status, conversationId) are already documented with sourcing hints. The description adds no filtering semantics, default sort, or pagination guidance beyond the schema, so the baseline 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?

The description defines the resource precisely — meetings booked out of conversations or created in the web app — which is more informative than a generic 'list appointments'. It also implicitly scopes itself against write tools by stating none exist. It stops short of stating the verb/return shape (a paginated collection) in the description itself, relying on the title for that.

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?

Explicitly rules out creation/editing ('there is no tool to create, change or cancel one') and routes the agent to `conversation_get` when the underlying thread is wanted. It does not, however, contrast with the sibling `appointment_get`, so an agent choosing between fetching one appointment vs listing many gets no guidance.

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