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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is covered. The description adds genuinely non-obvious context beyond that: the distinction between `quantity` (seconds) and `quantity_in_hours` (hours), which is a real trap in the returned data, plus the underlying endpoint. It stops short of noting pagination caps or rate limits.

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 compact sentences with no filler: what it lists and returns, what you can filter on, and one unit caveat. The core purpose is front-loaded and everything after it earns its place.

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 and 13 optional parameters, the description plus the fully-described schema gives an agent everything needed to call it. The only minor gap is that pagination behavior (page_token/offset interplay, the 10,000-record cap) is left entirely to schema descriptions rather than surfaced in the prose.

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 one of the 13 parameters is already documented with enums, defaults, and bounds. The description restates the filterable dimensions but adds no formatting or constraint detail beyond the schema; the seconds/hours note concerns return fields, not parameters. 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?

States a specific verb and resource ('List activities') and enumerates the three kinds of records returned (time entries, expense entries, fixed fees) along with the fields surfaced (hours, rate, total, billing status). This clearly separates it from write-side siblings such as clio_create_time_entry and from clio_list_bills.

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 sentence 'Filter by matter, user, type, status or date range' implies how the tool is used, but it never says when to pick this tool over alternatives (e.g., clio_list_bills for billing data, or clio_get_matter for a single matter's context). Usage is inferable but no exclusions or alternatives are named.

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