get_sessions

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

No annotations are provided, so the description carries full burden. It describes that sessions track memories and that this tool returns recent sessions, but it lacks behavioral details such as whether it is read-only, if there is pagination, or any side effects. The existence of an output schema partially compensates, but the description itself is minimal on behavioral disclosure.

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 three sentences long, with the primary action in the first sentence. It is concise, front-loaded, and every sentence adds value without redundancy.

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 relatively simple tool with two optional parameters and an output schema, the description provides sufficient context: it explains what sessions are and how to use the tool. It could mention that it returns a list of sessions, but the output schema likely covers that. Overall, it feels complete enough for most use cases.

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?

Both parameters (limit, project_path) have descriptions in the input schema (100% coverage), so the schema already documents them. The description does not add any additional parameter guidance, which meets the baseline expectation for high schema coverage.

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: 'Get recent conversation sessions.' It also provides context on what sessions are. While it hints at navigation, it doesn't explicitly differentiate from siblings like get_session, so sibling distinction is somewhat implicit.

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 says 'Use this to see conversation history and navigate to specific sessions,' which provides basic usage guidance. However, it does not mention when not to use this tool or explicitly point to alternatives (e.g., get_session for a single session).

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