Switch Organization

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

Discloses that the tool returns and automatically sets a new access token, which is useful behavioral info. However, lacks details on whether the old token is invalidated, permission requirements, or other side effects. No annotations exist to compensate.

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?

Two concise sentences that front-load purpose and outcome. No unnecessary words or repetition.

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 tool's simplicity (one parameter, no output schema), the description covers core behavior and result. Could mention post-switch implications (e.g., future calls use new token) but is largely sufficient.

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% with a clear description for orgId. The description does not add additional meaning beyond the schema (e.g., format, how to obtain ID). Baseline 3 is appropriate.

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?

Clearly states the action 'Switch to a different organization', identifies the resource, and specifies the outcome (returns and sets a new access token). Distinct from siblings like neuron_list_organizations.

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?

Provides the usage context (switching orgs) but no guidance on when to use versus alternatives, no prerequisites (e.g., existing organization list), and no exclusions.

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