activate_quick_roles

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

With no annotations, the description carries the behavioral disclosure burden. It adds useful context by noting that the tool 'Reads the latest config each time' and requires no server reload. However, it does not disclose side effects beyond activation, such as permission requirements, audit implications, or what happens when no quick roles are configured.

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 three short, purposeful sentences with no filler. The core action and purpose are front-loaded, followed by prerequisite setup and a useful configuration note.

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 low-complexity tool with two optional parameters and no output schema, the description provides the essential setup context and behavioral note. It is sufficient for an agent to invoke the tool correctly, though it could mention the no-roles-configured edge case.

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%, and the description does not add parameter-specific meaning beyond the schema. The baseline of 3 applies because the schema already documents duration and justification clearly.

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 states a specific verb ('Activates'), a specific resource ('your saved quick roles (favorites)'), and the purpose ('for fast elevation'). It is distinguishable from activate_pim_roles by focusing on saved favorites, though it does not explicitly contrast itself with that sibling.

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 gives clear setup context: configure quick roles first using list_quick_roles and save_quick_roles. It also explains the dynamic-config behavior, but it does not state explicit conditions for choosing this over activate_pim_roles or other siblings.

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