state_list

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

With no annotations provided, the description carries the full burden, and it does disclose key behavioral traits: it lists 'all' saved snapshots and the sort order ('by capture date'). This implicitly confirms it is a read-only operation. However, it does not explicitly mention the return format or error behavior, keeping it from a perfect score.

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 a single, focused sentence with no wasted words. It leads with the verb 'List' and includes only essential information about scope and ordering.

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?

Despite lacking an output schema or annotations, the tool is simple and the description is sufficient for an agent to understand what it does and when to invoke it. It could be improved by specifying the return format (e.g., array of snapshot IDs), but overall it is complete enough given the low complexity.

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?

The tool takes zero parameters, so the schema provides complete coverage. The description adds no parameter details, but since there are none, the baseline of 4 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?

The description uses a specific verb 'List' with a resource 'saved chart state snapshots' and adds detail about sorting by capture date. This clearly distinguishes it from sibling state_* tools like state_snapshot, state_restore, and state_delete.

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 clearly implies when to use it (when you need to see saved snapshots), providing clear context without explicitly excluding alternatives. It does not state when not to use it, but for a simple list tool, the implied usage is sufficient.

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