list_backups

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

Description indicates it is a read operation (list, show). No annotations provided, so description carries burden. It doesn't mention any side effects, which is fine. However, it doesn't clarify that backups are per-server or globally, which might be nuanced.

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. Front-loaded with 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?

The description is minimal but functional. However, it lacks details about the output format (e.g., what fields are in each backup entry). No output schema exists, so description should compensate. It does not mention whether it lists backups from all servers or just the default. Parameter behavior is left to schema.

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 description covers the 'server' parameter thoroughly. Tool description adds no new parameter semantics, but baseline is 3 due to high schema coverage.

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 'list' and resource 'Webmin configuration backups'. Distinguishes from other list tools by specifying backups.

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 on when to use this vs other list tools. No exclusions or prerequisites.

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