session_info

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

No annotations are provided, so the description carries the full burden. It discloses return fields and the key behavior that logs are recorded continuously, including boot logs. It does not explicitly state side effects or permissions, but as a metadata query it is implicitly safe and read-only. This is more transparent than many descriptions.

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 sentences, front-loaded with the core purpose, then parameter behavior, then return details. Every sentence earns its place, with no redundant or filler content.

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 the tool's simplicity (two optional params, no output schema), the description is complete. It covers all parameter combinations, lists all return fields, and includes important behavioral context about log recording. No significant gaps.

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 coverage is 100% with descriptions for both parameters. The description adds value by explaining the 'neither' case and describing the return structure, which goes beyond the schema's brief parameter descriptions. It clarifies the filtering semantics effectively.

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 the tool's purpose: 'Query active session metadata.' It uses a specific verb (Query) and resource (active session metadata), and distinguishes itself from sibling tools which are all about shell/connection operations rather than metadata lookup.

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 explains the parameter combinations: 'Pass session_id for one session, device for all sessions of a device, or neither for all active sessions.' This gives clear context on how to use the tool, though it does not explicitly exclude alternatives or mention when not to use it. However, the distinction from the sibling action tools is implicit and clear enough.

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