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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and openWorld, so the safety profile is covered. The description adds useful context beyond that: the scope is limited to this firm's users, and the returned ids are foreign keys consumed by other operations. It says nothing about result volume or rate limits, keeping it short of exhaustive.

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?

A single compact sentence plus the underlying endpoint. The identifying purpose and the downstream-use hint are both front-loaded, and no sentence is filler.

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 seven optional parameters, all schema-documented, and no output schema, the description covers what an agent needs to select and call it. It omits any mention of the paginated response shape (next_page.page_token), though the schema's page_token description largely compensates.

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%, including enum values for role and subscription_type and pagination semantics for page_token and limit. The description adds no parameter-level detail, which is acceptable given the schema does the heavy lifting, but it earns no credit above baseline.

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 (list) and resource (the firm's Clio users), and clarifies the population as attorneys and staff, which disambiguates from generic 'users'. It does not name any sibling for contrast, but the resource is distinct enough from the other list_* tools that confusion is unlikely.

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 clause 'use their ids for responsible attorneys, time entries and task assignees' tells the agent exactly why and when to reach for this tool — before create_matter, create_time_entry, or create_task that need an assignee id. It stops short of stating exclusions or naming alternatives, so it is strong context rather than full routing guidance.

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