discover_hermes_sessions

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

Annotations already indicate read-only, non-destructive, idempotent, and closed-world. The description adds valuable context: it scans $HERMES_HOME, returns JSON with specific fields, and notes global scope. No mention of performance or auth, but annotations reduce burden.

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 two sentences, front-loaded with purpose and scope. Every sentence adds value: first defines action, second details scanning and return structure. No wasted words.

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?

Although there is no output schema, the description explains the return JSON structure. It covers scanning paths and global behavior. It omits possible error cases (e.g., missing $HERMES_HOME), but for a simple list tool, it is largely complete.

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%, so the schema already documents all three parameters. The description adds no parameter-level information beyond what the schema provides, warranting the baseline score of 3.

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 lists Hermes Agent sessions, specifying verb ('List'), resource ('Hermes Agent sessions'), and scope ('visible on this machine', 'GLOBAL'). It differentiates from siblings by emphasizing results are not filtered by current project, contrasting with tools like 'search_sessions'.

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 implies usage for a global view of sessions but does not explicitly state when to use alternatives or when not to use this tool. Siblings like 'search_sessions' exist for filtered queries, but no guidance is provided.

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