list_sessions

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

With no annotations provided, the description carries full burden for behavioral disclosure. It only says 'recent' without defining the timeframe (e.g., last hour, last 24 hours). It doesn't mention ordering, pagination, error conditions, or whether any state is mutated.

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 one short sentence, which is concise but lacks substance. It is front-loaded with the verb 'List', but omits important details. While it avoids verbosity, it could be longer to include parameter and usage details.

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?

There is no output schema, so the description should explain the return format beyond 'cost and token totals'. It does not mention whether results are sorted, if sessions include metadata like IDs or timestamps, or how 'recent' is determined. For a listing tool, more context is needed.

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 0%, and the description does not mention the 'limit' parameter at all. It adds no value beyond what the schema itself provides (type, default, min/max). The description should explain how 'limit' affects the result.

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 action ('List') and the resource ('recent sessions'), and mentions the output includes cost and token totals. Among sibling tools (export_csv, get_hint_detail, etc.), 'list_sessions' is uniquely about sessions, so it is distinguishable.

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 guidance on when to use this tool versus alternatives. The description does not provide context such as prerequisites, typical use cases, or when not to use it. For example, it doesn't clarify if this is for auditing, monitoring, or debugging.

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