List backups

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

Discloses ordering (most-recent first) and that response shape depends on AMP's plugin. No annotations provided, but for a read-like list tool, this is transparent. Could mention if it's read-only or requires auth.

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?

Extremely concise, two sentences with no filler. Front-loaded with key information.

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 low complexity and good schema coverage, description is mostly complete. Could mention error handling for invalid instanceId or no backups, but not essential for a simple list 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 already describes instanceId as UUID from amp_list_instances (100% coverage). Description adds no extra meaning beyond referencing the instance. Baseline score appropriate.

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?

Description clearly states the action (list) and resource (local backups for one AMP instance), and distinguishes from other tools like amp_list_instances. It specifies ordering and return shape.

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?

Implies usage when needing backups for a specific instance, but does not explicitly mention when not to use or alternatives like other list tools. Adequate without exclusions.

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