clients_list

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

The description adds one behavioral detail: automatic pagination. However, with no annotations, it does not disclose read-only nature, permission requirements, or other side effects. This is minimal transparency beyond the schema.

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?

Two short sentences with no redundancy. Purpose is stated first, followed by a key behavioral trait. Every word 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?

For a list tool, the description is adequate but minimal. It explains what the tool does and pagination, but lacks information about the response format or what fields are returned. Given no output schema, a hint about the return structure would improve completeness.

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 coverage is 100%, so the baseline is 3. The description mentions pagination behavior, which relates to maxPages and pageToken, but does not add significant meaning beyond the schema descriptions.

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?

Description clearly states the tool lists GTM clients in a workspace. The verb 'list' and resource 'GTM clients' are specific, and the scope 'in a workspace' is narrow. It implicitly distinguishes from single-resource tools like clients_get, but doesn't explicitly differentiate from other list tools.

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 on when to use this tool versus alternatives (e.g., clients_get for a single client, or other listing tools). No prerequisites or context for usage are provided.

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