rba_list_autoexec_backups

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states that the tool lists sidecar backups, but does not reveal the output format, whether it is read-only, or how it behaves when targetPath is empty. This is a minimal description that adds little beyond the tool's name.

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 that is front-loaded with the action verb 'List'. It contains no wasted words and efficiently conveys the core purpose.

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 that there is no output schema, no annotations, and no parameter descriptions, the description is quite incomplete. It leaves critical questions unanswered, such as what the returned backup list looks like and what constitutes a 'sidecar backup' in this context.

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 has one parameter (targetPath) with no description (0% coverage), so the tool description must compensate. It hints that targetPath refers to the 'autoexec target', but does not specify the expected format, whether it is required, or what happens when left empty.

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 (sidecar backups for an autoexec target), which distinguishes it from the more generic sibling rba_list_backups. It is specific and unambiguous about what the tool does, though it does not elaborate on what a sidecar backup is.

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 is provided about when to use this tool versus alternatives like rba_list_backups or rba_restore_autoexec_backup. The usage context is implied by the name and description, but there is no explicit 'use this when' or mention of prerequisites.

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