switch_site

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

With no annotations, the description carries the disclosure burden and does reveal key behavioral traits: subsequent calls target the new site and the selection is saved locally for auto-connect next session. It does not cover failure modes, permissions, or return values, but the most important state-changing behavior is transparent.

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 four short sentences with no filler. It front-loads the action, then explains the session and persistence implications, and ends with a concrete 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?

For a single-parameter state-switching tool, the description covers what it does, how it affects subsequent calls, persistence behavior, and how to obtain the parameter. No output schema is needed, and the description is sufficiently complete to invoke the tool safely.

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 schema already documents site_id, but the description adds practical guidance by instructing the user to call list_my_sites first to retrieve it. This provides meaning beyond the schema's terse 'The site ID to switch to.'

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 opens with a specific verb and resource: 'Switch to a different site by site_id.' It distinguishes the tool by stating its persistent effect on subsequent calls, making its purpose unambiguous relative to the extensive sibling list.

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 context, including that all subsequent calls will target the new site and that the choice persists across sessions. It also directs the user to 'Use list_my_sites first to find the site_id,' but it does not explicitly mention when not to use the tool or name alternative tools for the same action.

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