list_capsules

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

No annotations are provided, so the description carries the full burden. 'List all saved experiment capsules' discloses that the operation is a read-only enumeration and scopes the result set to saved capsules, but it does not mention return ordering, output format, pagination, or potential side effects. The non-destructive nature is inherent in the verb 'list' and an output schema exists, so this is adequate but minimal.

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 front-loaded sentence with no wasted words. It states the verb and resource directly, making it optimally concise for a zero-parameter list tool.

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?

Given the extremely low complexity—zero parameters, simple list operation, and an existing output schema—the description covers everything an agent needs to call the tool correctly. Sibling tools are distinguishable by their names and descriptions, so no additional context is required.

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, and the input schema is fully covered (100%). With no parameters to document, the description appropriately adds no parameter details; the baseline for zero-parameter tools is 4.

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 the specific verb 'List' with the resource 'all saved experiment capsules', making the tool's function immediately clear. It is easily distinguished from sibling capsule-related tools such as create_capsule, load_capsule, delete_capsule, and compare_capsules.

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 the tool—when you need to enumerate all saved experiment capsules—but it does not explicitly state exclusions or alternatives. It does not mention that compare_capsules might be used for comparing capsules or load_capsule for loading a specific one, so guidance is only implied.

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