entitlement_remove

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

Beyond the annotations (readOnlyHint=false, destructiveHint=true, idempotentHint=true), the description adds meaningful behavioral detail: it mentions the tool is audited and that confirm=False offers a preview dry-run, both of which are valuable to an agent.

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 compact and well-structured: a one-line summary, a short usage note, and a bullet-like Args list. Every sentence adds value without redundancy.

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 purpose, params, and behavioral nuance, but it does not mention return values (e.g., whether it returns a task ID or a simple success message) or potential error cases. Given the absence of an output schema, this is a modest gap.

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?

With 0% schema coverage, the description carries the full burden of explaining parameters. It describes each parameter with usage context—pool_id from pool_list, ad_user_or_group_ids from entitlement_list, confirm's preview/revoke effect, and target's default behavior.

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 "[WRITE] Revoke desktop-pool access from AD user/group SID(s)", which is a specific verb+resource statement clearly distinguishing this from sibling tools like entitlement_add. The scope and intent are unambiguous.

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 instructs users to get SIDs from entitlement_list and explains that confirm=False previews while confirm=True revokes. This provides clear context but stops short of explicitly naming alternatives or when-not-to-use conditions.

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