get_customer_clients

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

With no annotations, the description carries full burden but only states it 'lists subaccounts'. It fails to disclose important behaviors such as default parameter values, pagination via 'limit', filtering options (status, direct_only, include_hidden, include_self), or any side effects. The agent lacks crucial operational details.

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 a single sentence, which is concise, but it sacrifices necessary detail. It could include more context without being verbose, especially given the 7-parameter schema and sibling tools. It is not front-loaded with critical information.

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?

Given the tool has 7 parameters and no parameter descriptions in the schema, the description is insufficiently complete. While an output schema exists, the lack of parameter explanations and behavioral cues means the agent cannot effectively use the tool without external knowledge. The description needs to cover the role of key parameters.

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%, yet the description adds no explanation for any of the 7 parameters. Parameters like 'customer_id', 'status', 'direct_only', etc., are not mentioned, leaving their semantics entirely unclear. The tool name and description do not even hint at the filtering capabilities.

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 the action ('List subaccounts') and the resource ('customer_client') with a specific context ('under a manager account'). It differentiates from the sibling 'find_customer_clients' by implying a straightforward listing rather than a search.

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 provides no guidance on when to use this tool versus its sibling 'find_customer_clients' or other tools. It does not mention prerequisites, limitations, or context for use, leaving the agent to infer.

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