Select administration

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

The annotations already provide readOnly, idempotent, and non-destructive hints. The description adds the key behavioral fact that the change is session-scoped and affects subsequent tool calls, which goes beyond the structured annotations. 'Change' sits slightly awkwardly with readOnlyHint if interpreted strictly, but no external data mutation is implied.

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 tight sentences. The first names the action and the condition, the second gives the persistence scope. 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-parameter session-state setter with full schema coverage, the description tells the agent what it does, when it matters, and how long it lasts. An output schema is unnecessary because the outcome is a session setting rather than a returned resource.

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 fully describes the only parameter and even references list_administrations as the source. The description adds no additional parameter meaning, so the baseline of 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 precise action ('change the administration that tools use'), the condition ('when they are not given an explicit administration_id'), and the session scope. This clearly distinguishes it from list_administrations and other resource-specific sibling tools.

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?

Explains when the effect applies (when no explicit administration_id is passed) and that it lasts for the rest of the session. It doesn't explicitly name alternatives, but the session-default behavior is self-contained and the parameter schema points to list_administrations as the id source.

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