GetSession

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

The description includes '[read-only]' upfront, signaling the tool is non-destructive. It also explains the output includes session ID and state. No annotations are provided, so the description carries the full burden and does so adequately.

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 front-loaded with '[read-only]'. Every phrase adds value with no redundant information.

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 tool with low complexity (one optional parameter, no output schema), the description fully covers purpose, usage, and behavioral transparency. It even mentions what is returned (session ID, state, cookies, CSRF token), making it complete.

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 100% as the only parameter 'force_new' has a description in the schema. The tool description does not add additional meaning beyond the schema, so the baseline score of 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?

The description clearly states the verb 'Get' and the resource 'Session', specifying it retrieves a new session ID and current session state (cookies, CSRF token). It distinguishes itself from sibling 'Get*' tools by being the only session-related tool.

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 explicitly says 'Use this to maintain the same session and lock handle across multiple requests,' giving clear context for when to use it. It implies it should be called before other ADT operations but does not explicitly state when not to use or provide alternative tools.

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