openclaw_sessions_compaction_list

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

States 'Read-only' which is a key behavioral trait, especially with no annotations. However, lacks further details like idempotency, rate limits, or side effects. Acceptable for a list operation but could be more complete.

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 concise sentences, front-loaded with the verb and resource. No redundant information. Highly efficient.

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?

No output schema, and description doesn't specify return format (e.g., array of snapshot objects, fields). Missing info on pagination or filtering. Adequate for a simple list but could be more 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% with descriptions for both parameters. Description adds no extra meaning beyond schema. Baseline score of 3 applies.

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?

Clearly states action ('List'), resource ('compaction snapshots for a session'), and distinguishes from sibling compaction tools like get/restore/branch. Also notes it's read-only, providing immediate clarity.

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?

Implied use case (listing snapshots for a session) but no explicit when-to-use or when-not-to-use guidance. No alternatives mentioned among siblings, e.g., when to use this vs openclaw_sessions_compaction_get.

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