activate_pim_roles

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool activates roles but doesn't disclose important behavioral traits: whether activation is immediate, whether it checks eligibility first, what happens on failure, or whether it requires approval. The phrase 'match against your eligible roles' hints at validation behavior but doesn't explain the consequences of mismatches or partial failures.

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 a single sentence that front-loads the core action and resource. It's concise and to the point, with no wasted words. The second sentence adds useful context about matching eligible roles. It could be slightly more structured by separating the usage guidance, but overall it's efficient.

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?

For a mutation tool with no annotations and no output schema, the description is incomplete. It doesn't explain what happens after activation (e.g., confirmation, errors, approval workflows), how scopes are specified, or how this differs from activate_quick_roles. The sibling list includes activate_quick_roles, which likely overlaps in functionality, and the description doesn't help an agent choose between them. The tool has 3 parameters and 2 required, so more behavioral context is needed.

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 100%, so the schema already documents all three parameters. The description adds minimal value beyond the schema: it mentions 'role names and scopes' but the schema only has a 'roles' array and no explicit 'scopes' parameter. This creates slight ambiguity about whether scopes are embedded in role names or a separate concept. The description doesn't clarify the 'duration' or 'justification' parameters beyond what the schema already states.

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 activates specified PIM roles in Azure, with a specific verb ('activates') and resource ('PIM roles'). It distinguishes itself from sibling tools like list_eligible_roles by focusing on activation, though it doesn't explicitly name alternatives. The mention of 'match against your eligible roles' adds useful context about how the tool works.

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 usage context: provide role names and scopes to match eligible roles. It doesn't explicitly state when to use this tool versus alternatives like activate_quick_roles, which appears to be a sibling that also activates roles. The lack of explicit when/when-not guidance leaves some ambiguity, but the description does convey the core usage pattern.

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