passgage_switch_to_user_mode

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 a prerequisite but does not reveal behavior when the prerequisite is unmet (e.g., error, no-op), whether a switch invalidates existing auth state, or other side effects. This is too sparse for a state-changing operation.

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, front-loaded sentence with no unnecessary words. It efficiently conveys both the action and the key prerequisite.

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 simple with no parameters or output schema, but the description lacks details about failure modes or exact state changes. It communicates the core function but not enough for an agent to predict behavior when prerequisites are unmet. Given the low complexity, it is minimally viable but not complete.

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 tool has zero parameters, so the schema provides no semantic detail. The baseline for 0 params is 4, and the description does not need to compensate for missing parameter information.

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 uses the specific verb 'Switch' and identifies the resource as 'user JWT authentication mode,' clearly distinguishing it from the sibling 'passgage_switch_to_company_mode'. It also adds a prerequisite (requires previous user login), enhancing clarity.

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 by stating a prerequisite (requires previous user login) but does not explicitly contrast with alternatives like switching to company mode or specify when not to use it. The mode-switching context gives some implied guidance, but no explicit when/when-not or alternative references.

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