install_seb_extension

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

No annotations are provided, so the description carries the full burden. It discloses that the operation is a force-install at the OU level, but does not mention permission requirements, reversibility, potential disruption to existing extension settings, or failure behavior. The rationale about data masking is purpose context, not behavioral transparency.

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 sentences with a clear action verb and a rationale. No fluff; the second sentence earns its place by conveying the business need for the force-install.

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?

The description covers the purpose and a use-case trigger but omits safety/behavioral details that are important for a mutation tool with no annotations. The existing output schema may account for return values, but prerequisites and side effects remain unexplained.

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?

Both parameters are fully described in the schema (100% coverage), so the baseline is 3. The description does not add extra meaning beyond the schema's orgUnitId and customerId 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?

The description starts with 'Force-installs the Secure Enterprise Browser (SEB) extension for a given Organizational Unit,' which is a specific verb+resource+scope. It clearly differentiates from sibling tools like install_ev_extension by naming the SEB extension.

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 second sentence provides a clear context cue: the SEB extension is REQUIRED for advanced Chrome Enterprise Premium features like data masking. However, it does not explicitly state when not to use this tool or name alternatives such as check_seb_extension_status or install_ev_extension.

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