Session status

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

The readOnlyHint=true annotation already establishes this as a non-mutating read, and the description adds a genuine privacy disclosure ('Returns no personal data') that annotations do not cover. It omits what the response actually looks like (a validity flag plus expiry timestamp) and what happens when no session is saved.

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 short sentences with zero waste; the core check (validity) is front-loaded ahead of the secondary detail (token expiry) and the privacy note.

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?

With no output schema, the description carries the burden of describing return values, and it does so only partially — an agent knows it gets validity and expiry, but not the shape of the response or how the 'not logged in' case is reported. Adequate for a simple zero-param status probe, but not 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?

The tool takes zero parameters, which is the baseline-4 case. There is no parameter syntax to explain, and the description correctly does not invent any.

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?

States a specific verb and resource: check the saved platform session's validity and access-token expiry. Neither the name nor the title alone would convey the token-expiry aspect, so the description adds real information, and no sibling tool overlaps with this diagnostic role.

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 usage is implied — an agent would naturally call this to verify session state before other browser-backed calls — but the description never says when to use it, when not to, or what to do on an invalid result. There are no sibling alternatives to route to, which limits how much guidance is even possible.

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