Explain what a browser session did

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

Annotations already declare readOnlyHint and idempotentHint, and the description reinforces safety with 'Read' and 'never starts a browser.' It adds a useful behavioral boundary that is not fully captured by the annotations alone: no browser is launched during invocation.

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?

One short sentence delivers the core action, the scope, and a key exclusion. Every word earns its place, and the most important behavior is front-loaded.

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 read-only diagnostics tool with no required parameters, the description plus annotations provide enough context for selection and safe invocation. A bit more detail about what 'activity' includes or how output is returned would help, but the absence is not critical given the schema and annotations.

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%, so the parameters are fully documented there. The description's 'live/released activity' and 'list live handles' loosely map to session_id, steel_session_id, and list_live, but it adds no parameter-level detail beyond what the schema already provides.

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 names a specific operation and resource: 'Read live/released activity or list live handles.' It also distinguishes itself from sibling tools by adding 'never starts a browser,' which separates it from session-creating or browser-acting 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?

The description clearly indicates this tool is for reading diagnostics or listing live handles, not for launching a browser. However, it does not explicitly name siblings like steel_session_live_view or steel_session_replay, leaving some routing to the agent's inference.

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