timeiq_client_list

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

No annotations are provided, and the description does not disclose behavioral traits such as pagination, sorting, limits, or whether the list returns all clients. This leaves the agent uninformed about the tool's behavior beyond basic listing.

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 extremely concise with a single sentence that efficiently conveys both purpose and available parameters. No unnecessary words or redundancy.

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?

For a simple list tool with one parameter, the description covers the essential purpose and parameter. However, it lacks information about return structure, pagination, or constraints, making it minimally complete but with gaps.

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?

The description explicitly lists the filter options and their intended use ('active, archived, managed, or managed_archived'), adding meaning beyond the schema's enum list. However, it does not explain the semantics of each filter (e.g., what 'managed' means) in detail.

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 clearly states 'List clients' as the verb and resource, and specifies the filtering options (active, archived, managed, managed_archived). This differentiates it from sibling tools like timeiq_client_get (single client) and timeiq_client_activate/archive (mutations).

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 implicitly indicates that this tool is for listing clients with filters, but it lacks explicit guidance on when to use this over alternatives like timeiq_client_get for retrieving a single client. No when-not-to-use or context is provided.

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