reload_session

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

The description discloses the internal behavior of reading .env variables and rebuilding the HTTP session, adding meaningful context beyond the annotations. With annotations already present, this is sufficient and does not contradict any hints.

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; the action is front-loaded and every sentence earns its place. No redundant details or schema 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?

For a zero-parameter tool with an output schema, the description fully covers what it does, when to use it, and the key constraint. Nothing necessary for correct invocation is missing.

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?

There are no parameters, so the schema already fully communicates the zero-argument contract. The description reinforces this with 'Never pass cookie values as arguments,' which is especially valuable and prevents a common misuse.

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?

Description uses a specific verb phrase ('Re-read .env' and 'rebuild the HTTP session') and names the exact resource/env vars involved. It is clearly distinguished from sibling tools like check_session and log_out by the reload/rebuild 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?

Provides an explicit trigger: 'Use this after the user updates cookies on disk.' It also gives a clear negative directive ('Never pass cookie values as arguments'), though it does not explicitly name alternative sibling tools or when-not-to-use conditions.

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