clio_list_users

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

Annotations already carry the safety profile (readOnlyHint=true, idempotentHint=true, destructiveHint=false). The description adds a genuinely useful behavioral trait — that it 'routes only through the exact project/account governed connector authority' — and clarifies that Spring verifies the read effect. This is comparable to the calibration baseline: useful context beyond annotations, but no detail on failure modes or pagination.

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?

The description is compact and well-structured: a one-line identity statement, a single routing-constraint sentence, followed by a scannable arg list. Every element earns its place and the parameter documentation is front-loaded rather than buried.

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?

The output schema exists, so return values need no explanation, and the parameter list is fully enumerated. The main missing piece is the content contract for the 'arguments' JSON string — the actual operational payload an agent must construct to list users — plus any guidance on when this tool is appropriate. Adequate for a generic connector wrapper, but with a clear gap in invocation-critical detail.

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 0%, so the description carries the full burden, and it does document all 7 parameters with at least a phrase each (e.g., 'Authenticated Project UUID', 'Project-bound connector account alias'). However, the two most operationally important parameters are thin: 'arguments' is only 'JSON string of arguments for the connector operation' with no hint of what the list_users operation expects inside, and 'project_ref' as 'Exact project correlation reference' remains opaque.

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 identifies the tool as 'Clio connector operation `list_users`', which largely restates the name rather than stating an independent purpose like 'Lists users from the connected Clio account'. The routing sentence adds context about governed connector authority, but the core purpose is conveyed by the name itself, not the description.

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?

No guidance is given on when to use clio_list_users versus sibling alternatives such as clio_get_user, clio_list_contacts, or the clio_search tool. There are no usage conditions, exclusions, or stated distinctions from other Clio connector operations, so the agent must infer usage entirely from the tool name.

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