rba_list_capsule_snapshots

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

Without annotations, the description does not disclose behavioral details such as read-only status, error handling, or requirements (e.g., capsule existence). The verb 'List' implies a read operation, but no explicit safety or behavior information is given, so the description does not fully carry the burden.

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 concise sentence front-loaded with the action verb. It contains no filler and is easy to parse, making every word earn its place.

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 simple one-parameter list tool, the description covers the basic purpose but omits potential return format, error scenarios, or prerequisites. With no output schema and no annotations, the agent has incomplete information, though the tool's simplicity mitigates the gap.

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 input schema provides only a bare 'id' field with length constraints and no description. The description adds context by indicating the tool operates on 'one RBA script capsule', implying that 'id' refers to the capsule's identifier. However, this is implicit rather than an explicit parameter description, leaving some ambiguity.

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 verb 'List' with a specific resource ('time-travel source snapshots') and scope ('for one RBA script capsule'), clearly distinguishing it from sibling tools that list all capsules or manage capsules. It directly states the tool's function and is not a tautology.

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 implies the use case (listing snapshots for a specific capsule) but provides no explicit guidance on when to use this tool instead of related tools like rba_list_script_capsules or rba_rollback_script_capsule. No alternatives or exclusions are mentioned, so the usage context is only implicit.

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