profile_use

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

No annotations are provided, so the description carries full behavioral disclosure. It states only the action ('Set the active profile') without describing whether it modifies global, per-session, or per-profile state or whether it has side effects on already-created sessions. It does not disclose the implications of changing the active 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?

A single, direct sentence with no filler. The parenthetical 'alias of session_use' demonstrates useful context without exploding length, front-loading the core action and important alias relationship.

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?

Given the minimal complexity and full schema coverage, the description is mostly sufficient to call the tool. However, it lacks the semantic context of what an 'active profile' affects—session targeting, default behavior, or interaction with session_use—making it incomplete for an agent without prior knowledge.

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?

Input schema covers 100% of parameter descriptions (name, lease, session), so a baseline of 3 applies. The description adds no explanation of the parameters beyond what the schema already provides, such as the meaning of 'lease' or session targeting.

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 identifies a clear verb-resource pair ('Set the active profile') and explicitly marks it as an alias of session_use, which helps differentiate it from profile_list, profile_new, etc. It does not fully explain the broader semantics of 'active profile', so it is slightly below a 5.

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 only states that it is an alias of session_use, but gives no guidance on when to use this tool over session_use or other profile tools. There is no mention of prerequisites, alternatives, or when it is appropriate to call it, leaving the agent without selection context.

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