switch_site

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

Annotations only declare readOnlyHint=false. The description adds two important behaviors beyond that: all subsequent tool calls target the new site, and the choice persists to local database for auto-connect next session. This is meaningful side-effect disclosure not derivable from annotations or 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?

Three sentences, front-loaded with the core action, then side effects, then the prerequisite helper. No filler or redundancy.

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 one-param switching tool with annotations, the description covers the action, session-wide consequence, persistence, and prerequisite discovery. No output schema exists, but the return is not crucial here; completeness is high though not exhaustive (e.g., what happens on invalid site_id).

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 coverage is 100% (the single site_id param is documented). The description says 'by site_id' and points to list_my_sites for finding it, which adds minimal value beyond the schema. Baseline 3 applies.

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?

States a specific verb+resource ('Switch to a different site') and its session-wide effect. Clearly distinguished from siblings like list_my_sites or create_site.

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?

Explicitly instructs to use list_my_sites first to find the site_id, giving a clear prerequisite and sequencing. It doesn't state when not to use it, but for a session-switching tool the guidance is solid.

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