list_backups

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

No annotations are provided, so the description carries the behavioral disclosure burden. It does disclose the HTTP method and the output fields, and the verb 'List' implies a read-only operation. It does not explicitly state that no side effects occur, nor does it mention ordering, limits, or failure modes, but for a zero-parameter list call this is adequate.

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 that states exactly what the tool does, the resource, the main output attributes, and the endpoint. There is no filler or redundant content.

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 parameterless list operation with no output schema, the description provides the essential information: what is listed, which attributes are returned, and the full endpoint. There are no nested objects, required parameters, or hidden settings that would require additional 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 tool has zero parameters and the schema coverage is 100%, so the description has no parameter semantics to add. Per the baseline for zero-parameter tools, this scores well because there are no undocumented inputs that could confuse an agent.

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'), a clear resource ('Tdarr database backups'), and enumerates the return fields ('name, size and date'). It also includes the exact endpoint, making the tool's purpose unambiguous and distinct from related backup tools like create_backup and delete_backup.

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 intended usage is implied by 'List the Tdarr database backups' — an agent should call this when it wants an inventory of backups. However, there is no explicit guidance about when not to use it or how it compares with sibling backup operations like get_backup_status or delete_backup.

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