x_snapshot_list

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

Annotations already establish read-only, idempotent, non-destructive behavior. The description adds the valuable behavioral fact that the tool never contacts X — meaning no network latency, no auth or rate-limit failure modes, and purely local data — which is not captured in the annotations.

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?

A single 8-word sentence with the verb and resource front-loaded; every word contributes meaning. No filler and no repetition of schema or annotation 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 one-optional-parameter list tool with a robust annotation profile, the description is nearly complete. The main gap is that it doesn't note the limit default behavior, though the schema covers that; return format is unaddressed but no output schema exists to anchor expectations.

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 coverage is 0%, so the description carries the burden, but it never explicitly names the limit parameter. 'Recent' only hints at the ordering/recency that limit interacts with; the parameter's meaning is mostly conveyed by the schema's own default/min/max constraints.

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 a specific verb and resource — 'list recent locally saved snapshots' — and adds the distinctive scope 'without contacting X.' This clearly separates it from siblings x_snapshot_read and x_snapshot_compare, both of which operate on specific snapshots rather than listing them.

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 phrase 'without contacting X' implies the tool is for offline/local listing when no network call is desired, but no alternative tools are named and no explicit when-not-to-use guidance is given. An agent must infer when to choose this over x_snapshot_read or x_snapshot_compare rather than being told.

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