Set user role

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

The description adds crucial behavioral information beyond the annotations, specifically stating that 'Other saved settings are retained,' which informs the agent that the change is focused and non-destructive to the entire profile. It also specifies that the tool returns 'the normalized role and computed emphasis,' detailing the output behavior despite lacking an output schema.

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 definition is well-structured, with each sentence serving a distinct and necessary purpose: function, alternative usage, return value, and scope limitation. It avoids jargon and provides flow, making it highly readable and 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?

Despite the lack of an output schema, the description is highly complete. It covers the functional goal, the specific parameters involved, the necessary contextual constraints (what it retains), and the expected return values. This makes it robust for an AI agent.

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?

Since the schema coverage is 100%, the schema already provides a robust description of the `role` parameter. The description reiterates this function but adds no semantic nuance or data handling context beyond what is already strictly defined in the structured input schema. This aligns with the baseline score for high coverage.

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 explicitly states the tool replaces the saved user role and defines its function as controlling dashboard sort and filter emphasis. It is highly specific and leaves no doubt about its core purpose.

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?

It provides clear usage guidelines by instructing the agent to use this tool for the user's 'chosen working role.' It also guides the agent to specific alternatives: `get_user_role` for inspection and `update_user_taste` for content preferences, ensuring correct tool selection.

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