adobe_remove_license

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

With no annotations provided, the description carries the burden of behavioral disclosure. It adds a rate limit (10/min per client, 100/min globally) and implies the action is a removal, but it does not mention side effects, idempotency, or error behavior (e.g., if the user is not in the profile).

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 concise and front-loaded with the primary action, then a rate limit note, then an Args section. Every sentence contributes value, and the structure is easy to parse.

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 core purpose, rate limit, and parameter meanings, and references a sibling tool for obtaining valid values. Given that an output schema exists, return values need not be explained. However, it omits edge-case behavior such as handling missing users, which prevents a perfect score.

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?

Schema description coverage is 0%, so the description must compensate. It explains both parameters: email is 'the user's email address to revoke the license from' and product_profile is 'the exact product profile name (see adobe_list_product_profiles).' This adds meaningful usage guidance 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 opens with 'Revoke a license by removing a user from a product profile,' which is a specific verb+resource statement that clearly differentiates it from siblings like adobe_assign_license. It conveys both the action and the mechanism.

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 context by noting the exact product profile name should be sourced from adobe_list_product_profiles, which is a useful usage hint. However, it does not explicitly contrast with alternatives or state when not to use it, though the purpose makes the primary use case evident.

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