nexalayer_rotate_session

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

Annotations already declare this is a non-read-only, idempotent, non-destructive, open-world operation, so the safety profile is covered externally. The description adds nothing about what rotation actually does to the session, whether the old credentials are invalidated, or what callers should expect, so it contributes almost no behavioral context beyond the structured 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?

A single front-loaded sentence with the action first and the trigger second; no filler. It is efficient, though it is arguably too short to carry the needed context.

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 mutating session-lifecycle tool with no output schema, 0% parameter documentation, and only generic annotations, a single sentence leaves too much unspecified: rotation semantics, the required idempotency_key, and the reason field are all unexplained.

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% and the description mentions none of the three parameters. session_id is loosely inferable from 'session', but idempotency_key (required, with length bounds) and reason are completely unaddressed, so the description does not compensate for the coverage gap.

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 ('Rotate') with a specific resource ('a dynamic session'), which an agent can distinguish from create_session and terminate_session. It stops short of explicitly contrasting itself with those siblings, but the action is unambiguous.

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?

It implies a trigger condition ('after health or telemetry recommends rotation'), which hints at using nexalayer_session_health first, but never names that sibling or states when NOT to rotate. Usage is implied rather than directed.

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