session_status

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

With no annotations, the description carries the full behavioral burden. It discloses that the tool starts nothing, that it reports when no browser is running, and why that state matters: 'If no browser is running yet it says so, because until one is running there is no identity to report.' This is strong side-effect and empty-state transparency.

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 front-loaded with the core purpose and stays reasonably concise. Each paragraph earns its place, though the opening is a sentence fragment and terms like 'exit' are used without immediate explanation.

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 parameterless status tool with an output schema, the description covers the essential points: what is reported, when to ask, how the seed relates to session_start, and what happens when no browser is running. Nothing critical is missing for an agent to invoke it correctly.

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 zero parameters and the schema is complete, so the baseline is 4. The description adds useful context about the session seed concept even though no parameters exist, which is appropriate for a parameterless status tool.

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 identifies the tool as a status reporter: 'Who is browsing right now: the identity, the exit, the profile and the tabs.' It also distinguishes itself by stating 'It starts nothing,' which separates it from session_start and other mutating session tools.

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 explicitly says when to use it: 'Ask whenever you need to know which person the browser currently is, or from where its traffic leaves.' It also explains the seed's role for replaying a session, but it does not explicitly contrast itself with sibling tools like session_list_pages, so the alternative routing is slightly implicit.

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