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

Annotations already declare readOnlyHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds useful behavior beyond that: results are ordered newest first and are scoped to enquiries from the caller's own agents, which tells the agent what to expect from the result set.

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 tight sentences: the scoping content comes first and the alternative tool is named at the end. Every sentence earns its place, with no restatement of the title or schema.

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 two-parameter read-only list tool this covers what the tool returns (recent enquiries, newest first) and how to drill down, with parameters handled by the schema. It never mentions pagination in prose, but offset/limit are fully documented in the schema, so that gap is minor.

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%, with limit (1–50, default 20) and offset documented inline, so the baseline is 3. The description adds no pagination or limit context of its own, so it neither compensates nor detracts.

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?

Specific verb and resource ('List recent customer enquiries'), plus concrete scope: which channels (website, phone, messaging) and who produced them (AI receptionist, phone agent). It is clearly distinguishable from the sibling get_conversation, which it names as the detail view.

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 explicitly routes the agent: use get_conversation with an id to read the full transcript, implying this tool is the browse/list step. No explicit 'when not to use' (e.g. filtering by lead or customer) is given, so it falls short of a 5.

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