list_org_units

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

No annotations are present, so the description carries the full burden. The verb 'Lists' implies a read-only operation, and the description mentions output content, but it does not explicitly state it is non-destructive, require specific permissions, or explain behavior when customerId is omitted. Adequate for a simple list tool but not detailed.

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 concise, front-loaded sentences convey purpose, usage context, and output value. No superfluous words or repetition.

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?

An output schema exists, so the return values are externally defined. The description provides essential context (what the OUs look like, why they are needed) and is appropriate for the tool's simplicity. The only minor gap is not clarifying the optional nature of customerId, but that is a small omission.

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 input schema already fully describes customerId with format example. The tool description does not add additional meaning beyond the schema, so the baseline of 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?

The description starts with 'Lists the Organizational Units (OUs)' - a specific verb and resource. It also explains the key outcome (provides orgUnitId, human-readable path, unique ID), distinguishing it from sibling list tools like list_customer_profiles.

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?

It explicitly says 'Use this tool to find the orgUnitId required by most other Chrome management and policy tools', providing clear context for when to use it. It does not mention alternatives or when not to use, but the guidance is direct and helpful.

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