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

Annotations already declare readOnly/idempotent/non-destructive and openWorld, so safety is covered. The description adds genuinely useful context beyond that: what records are being listed, which fields come back by default, and the underlying Clio endpoint (GET /communications.json), which helps an agent reason about scope. It stops short of describing pagination behavior or result caps.

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 first front-loads what is listed and what comes back, the second covers filtering and search. No filler, no redundancy with the title.

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 usefully names the returned fields, and annotations already cover the safety profile. For a 14-parameter list tool, the main remaining gap is that pagination and ordering workflow (page_token vs offset, the 10,000-record cap) is left entirely to the schema.

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 every parameter is already documented in-schema. The description only restates the filter categories in prose without adding syntax, defaults, or interaction details (e.g. how query combines with type). Baseline 3 is appropriate when the schema carries the load.

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?

States a specific verb and resource ('List logged communications — phone calls and emails recorded on matters') and enumerates the returned content (subject, body, date, senders, receivers). It implicitly contrasts with the write sibling clio_log_communication, but never names an alternative listing tool or clarifies scope boundaries explicitly.

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 lists the available filter dimensions (matter, contact, user, type, date range, subject/body search), which implies how to narrow results. However, it gives no explicit when-to-use versus when-not guidance, no mention of pagination workflow despite 14 params including page_token/offset, and no routing to a sibling.

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