adobe_assign_license

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

No annotations are provided, so the description must disclose behavior. It includes a rate limit (10 requests/min per client, 100/min globally) which is useful. However, it does not disclose side effects (e.g., consuming a license seat, irreversibility) or permission requirements, leaving a significant gap for a mutation tool.

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 the main action, followed by a rate-limiting note and concise parameter explanations. No wasted words; the example and cross-reference earn their 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?

Given the simple two-parameter tool with an output schema present, the description covers purpose, rate limit, and parameter semantics. It lacks error-case behavior or idempotency notes, but for this complexity level it is reasonably complete.

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 schema has no parameter descriptions (0% coverage), but the description explicitly explains both parameters: email is the user's email to grant the license, and product_profile must be the exact name, referencing adobe_list_product_profiles. This adds clear semantics beyond the raw schema.

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 license by adding a user to a product profile'), names the resource (license) and mechanism (adding to profile), and gives an example (Acrobat Pro profile). This distinguishes it from sibling tools like adobe_remove_license and adobe_list_users.

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 implies when to use this tool: whenever a license needs to be granted. It also provides a cross-reference to adobe_list_product_profiles for obtaining the exact profile name, which is helpful prerequisite guidance. However, it does not explicitly exclude cases (e.g., user already has a license) or directly compare with adobe_remove_license.

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