Auth Load Session

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so safety is covered. However, the description adds no behavioral context beyond the bare verb 'load'—it does not explain whether loading restores a previously saved session, whether it overwrites current state, what data is returned, or any prerequisites.

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?

At two words, the description is undeniably concise, but this is under-specification rather than efficient structure. A three-parameter tool with no output schema needs more than 'Load session.' to orient an agent.

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?

The description lacks essential context: what a session is, what is returned, how fields/output_mode/include_token affect the result, and when to use this instead of auth_status or auth_login. The presence of a rich sibling list and no output schema makes this brevity insufficient.

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 67%, with fields and output_mode documented, but include_token has no description. The tool description itself adds no parameter meaning, does not explain the effect of output_mode or fields, and fails to compensate for the undocumented include_token parameter.

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 states a verb ('Load') and a resource ('session'), so the basic action is identifiable. However, it is too vague to stand apart from sibling tools like auth_create_session, auth_save_session, and auth_status, and it does not clarify what 'session' means in this context or what loading entails.

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?

There is no guidance about when to call this tool versus the many auth-related siblings such as auth_save_session, auth_create_session, or auth_login. The name hints at a load-after-save workflow, but the description never states that intended usage or any exclusions.

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