ssh_backup_list

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

Explicitly states 'Read-only: it inspects the filesystem and mutates nothing.', which fully covers behavioral traits. Since no annotations are provided, the description compensates perfectly.

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?

Two sentences, no wasted words. First sentence covers action and return data, second covers safety and parameters. Highly efficient and front-loaded.

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?

No output schema, so description appropriately details return data (id, type, size, etc.) and clarifies behavior (read-only, default dir). Covers all necessary info for a listing tool.

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?

Schema coverage is 100%, but description adds value by clarifying the default for backupDir and explicitly listing the filter options (though schema has enum). This extra context aids correct parameter usage.

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?

Clearly states verb 'lists', resource 'backups found in backupDir on remote server', and distinguishes from siblings like ssh_backup_create by focusing on listing existing backups and parsing metadata.

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?

Explicitly notes read-only nature and optional type filter, but does not provide explicit guidance on when to use vs. alternatives like ssh_backup_create or ssh_backup_restore. Relies on context.

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