entitlement_add

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

Annotations already indicate a write operation (readOnlyHint=false) and idempotent (idempotentHint=true). The description adds behavioral details: confirm=False previews, confirm=True grants, and the operation is audited. This goes beyond the structured annotations and informs the agent of the actual execution semantics.

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, starting with a one-sentence purpose, followed by a short usage note, then a structured Args list. Every element adds value with no 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 tool is moderately complex with 4 params and no output schema. The description covers purpose, parameters, prerequisite lookups, and behavior. However, it doesn't specify the return format or response of preview/confirm actions, leaving a minor 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?

The input schema has no descriptions (0% coverage), so the description carries the full burden. It explains each parameter: pool_id from pool_list, ad_user_or_group_ids from ad_user_search, confirm's default and preview behavior, and target defaulting to config.yaml. This provides essential meaning 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 tool's function with a specific verb and resource: 'Grant desktop-pool access to AD user/group SID(s).' It also differentiates from sibling tools like entitlement_remove and entitlement_list by focusing on the add operation.

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 usage context by instructing to get SIDs from ad_user_search and pool_id from pool_list, and explains the confirm flag for preview versus actual grant. It implies this tool is for adding entitlements, though it doesn't explicitly exclude alternatives; still, the context is clear.

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