netlicensing_create_license

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

With no annotations, the description carries full burden. It discloses creation intent and conditional mandatory parameters, but omits behavioral traits like whether the operation is idempotent, if it modifies other resources, requires authentication, or triggers notifications. This is insufficient for a write operation.

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 front-loaded with a clear purpose sentence, followed by a well-structured list of parameters. Each line is concise. While slightly long (13 lines), it avoids fluff and uses a consistent format.

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?

Despite complexity (13 parameters, 2 required), the description covers most parameters with context. However, it lacks details on error conditions, output (though output schema exists), and global prerequisites. Overall adequate but not exhaustive.

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 has 0% coverage, so the description compensates well. It explains each parameter's purpose (e.g., 'licensee_number: Customer to assign the license to') and notes conditions (e.g., start_date mandatory for TIMEVOLUME type). This adds significant value beyond the schema's bare property list.

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: 'Assign a new license to a customer from a license template.' It includes a specific verb ('assign') and identifies the key resources (customer, license template). This distinguishes it from sibling tools like 'create_licensee' or 'create_license_template'.

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 explicit guidance on when to use this tool versus alternatives like 'netlicensing_update_license' or 'netlicensing_create_bundle'. It implies use when assigning a new license, but fails to mention exclusions or prerequisites (e.g., ensure customer and template exist).

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