assign_permission_set_license

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

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=true, so the safety profile is covered. The description adds a genuinely useful behavioral caveat (use the CLI username alias, not the User object's Alias field) but says nothing about required permissions, re-assignment behavior, or reversibility.

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 purpose is front-loaded in the first sentence, and every subsequent sentence carries syntax detail. Slight verbosity and mild redundancy in the closing sentence about onBehalfOf, but nothing that fails to earn 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 destructive, non-idempotent mutation with nested parameters and no output schema, the description covers the input syntax well but omits operational context such as permission requirements and what happens when a license is already assigned. Adequate but with clear gaps.

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?

Top-level schema description coverage is 0% for the sole 'input' wrapper, and the description compensates with real added meaning: alias semantics for targetOrg/onBehalfOf, repeated-array syntax for licenseNames, and quoting rules for names containing spaces. It goes beyond what the nested property descriptions convey.

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 ('Assign a permission set license') plus scope ('one or more org users'). It is clear what the tool does, but it never distinguishes itself from the sibling assign_permission_set, which is a subtly different operation an agent could easily confuse with this one.

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 guidance on when to use this tool versus assign_permission_set or any alternative, and no prerequisites or when-not conditions are given. The only usage-flavored text concerns alias and array syntax, which is parameter mechanics rather than tool selection.

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