pdm_pbs_snapshots_list

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

No annotations provided, so description carries full burden. Discloses read-only nature (list), empty datastore returns [], compatibility (Live-verified path PDM 1.1 -> PBS 4.2), and config requirement. Sufficient for a read diagnostic tool.

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?

Very concise: three lines, no wasted words. Purpose stated first, then parameters, then behavioral notes. Every sentence adds value.

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?

Covers purpose, parameters, compatibility, config requirement, and edge case (empty list). Output schema exists but not shown, so return details are omitted. For a simple list tool, it's fairly complete; could mention pagination or snapshot info level.

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 only 25% (proximo_target has description). Description adds meaning for remote, datastore (remote name, PBS datastore name), and ns (optional namespace filter). This compensates well for schema gaps.

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?

States 'list backup snapshots in a datastore on a PDM-registered PBS remote' – specific verb and resource. Distinguishes from pbs_snapshots_list by emphasizing PDM registration and 'DIAGNOSE (LOW)' label. Clearly describes scope.

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 for diagnosis (DIAGNOSE LOW) and requires PROXIMO_PDM_* config, but does not explicitly compare with pbs_snapshots_list or state when not to use. No alternative tool mentioned.

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