Load Auth Context

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

With no annotations provided, the description carries the full burden of disclosing behavior. It implies a mutation to the current session's auth state but does not explain effects (e.g., whether it replaces or merges existing auth), failure modes, or prerequisites. This is a significant gap for a tool that loads saved data.

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, concise sentence with no redundant words. It is front-loaded and clearly communicates the core action without wasted effort.

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 has two required parameters, no annotations, and an output schema (whose contents are unknown), the description is severely incomplete. It lacks usage context, behavioral details, parameter explanations, and any mention of prerequisites or side effects. For a tool that modifies session state, this is inadequate.

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 description coverage is 0%, so the description must compensate. It provides minimal mapping: 'saved auth context' → authContextId and 'current session' → sessionId, but it does not clarify parameter formats, allowed values, or how the two relate. This adds only marginal value beyond the raw schema.

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 a specific verb ('load') and resource ('auth context') with a clear target ('current session'), making the tool's purpose unambiguous. It distinguishes itself from sibling tools like save_auth_context, list_auth_contexts, and delete_auth_context through the 'load' action.

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 gives no guidance on when to use this tool versus alternatives, no prerequisites (e.g., existing session or saved auth context), and no exclusions. It merely states what the tool does without any contextual usage advice.

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