session_status

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

No annotations are provided, so the description must disclose behavior. It lists returned fields but does not explicitly state that the tool is read-only and has no side effects. The word 'health' implies a query, but without confirmation, an agent might not be sure if it triggers any state changes.

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 a single concise line listing all relevant fields. It contains no unnecessary words and is easy to scan.

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?

Given no output schema, the description is the only source for return format. It lists fields but lacks data types, structure description, or an example. For a health-check tool, it is somewhat complete but could be more helpful for agents to parse the response.

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 has zero parameters, and schema coverage is 100% (trivially). The description does not need to elaborate on parameters since none exist. No extra value is needed, but the description could clarify that no inputs are required.

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 states it returns session health with specific fields like alive, refsValid, lastSnapshotGeneration. It distinguishes from sibling tools (e.g., session_open, session_close) which modify state, so purpose is clear: read-only status check.

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?

No explicit guidance on when to use this tool vs alternatives. While it's implied for checking health before actions, the description does not mention when it is appropriate, when not to use it, or how it differs from other status-like tools (e.g., probe_help).

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