session

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

With no annotations, the description carries the burden for behavioral disclosure. It does disclose a 90-second timeout and that save-script does not close the session, which is useful. However, it does not disclose side effects, permissions, or the read-only nature of list/state-dir, which matters for a mixed read/mutation tool.

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 short and action-oriented, but the three modes are run together and 'Times out after 90s' is awkwardly appended without a clear separator. Better punctuation or a bulleted structure would make it easier to parse.

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?

This is a complex three-action tool with 18 parameters and no output schema. The description does not explain per-action parameter requirements, return values, or how the various selectors resolve to a device/session. The timeout and non-teardown note help, but substantial contextual gaps remain.

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 all 18 parameters are already documented by the input schema. The description adds no additional parameter-level meaning, so the baseline score of 3 is appropriate.

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 three concrete behaviors—list sessions, print the daemon state directory, and publish a save-script—with specific verbs and targets. It is reasonably distinguishable from sibling tools, though 'armed open-to-destination script' is jargon and the three modes are packed into one clause.

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?

There is no guidance on when to use this tool versus alternatives or how to choose among list/state-dir/save-script. The action enum provides some descriptions of each mode, but the main description does not explain selection context, prerequisites, or when another tool would be more appropriate.

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