get_sa360_customer_clients

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so safety behavior is covered structurally. The description adds only the hint that hierarchy levels are returned, and says nothing about pagination despite page_size/page_token parameters, nor about how deep the traversal goes.

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 front-loaded clause with no filler, and the key scoping word ('beneath') appears early. It is efficient, but its brevity comes at the cost of the guidance dimensions rather than being a deliberate tradeoff.

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 five-parameter SA360 hierarchy tool with zero schema descriptions, one sentence is not enough: the caller cannot tell what customer_id means versus account or login_customer_id, nor how pagination should be driven. The output schema covers return values, so that gap is excused, but the input-side gap is not.

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 burden for five parameters — including customer_id vs login_customer_id vs account, which are genuinely confusable in SA360. The description mentions none of them, leaving the manager-vs-login-account distinction entirely undocumented.

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 (discover client accounts beneath an SA360 manager) plus the notable attribute of hierarchy levels. It is distinguishable from list_sa360_customers by the 'beneath a manager' framing, though it never names or contrasts any sibling explicitly.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no pointer to list_sa360_customers or query_sa360 as the alternative for flat listings or performance data. An agent must infer from the phrase 'beneath a SA360 manager' that this is a hierarchy-expansion call.

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