direct.list_clients

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

No annotations are provided, so the description carries the full behavioral burden, yet it only says "List." It does not confirm read-only behavior, describe pagination behavior or defaults, or explain the agency/Client-Login auth context that governs this call.

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 short sentence with the key noun front-loaded and no filler. It is efficient, though it is arguably under-specified rather than deliberately minimal.

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 annotations and no output schema, the description should explain the return shape and the agency/account scoping behavior, but it does not. For a tool with nested parameters and a Client-Login override, this leaves important context to inference.

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 the schema already documents all five parameters including the pagination object, account_id, field_names, and the Direct Client-Login override. The description adds nothing beyond the field names, so the 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 Direct clients"), and the "(agency use)" qualifier hints at the scope. However, it does not distinguish itself from nearby-sounding siblings such as accounts.list or direct.list_campaigns, so an agent must infer the relationship from the parenthetical alone.

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 only guidance is "(agency use)," which faintly implies the tool belongs to an agency/multi-project workflow but names no alternatives and states no when-not condition. An agent cannot tell from this whether to prefer accounts.list or direct.raw_call for client lookups.

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