read_storage_snapshot

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds the useful constraint that no device connection is made, but says nothing about what a "record" contains, whether pagination results include a total, or how the snapshot is identified. Note a mild tension: openWorldHint=true sits oddly with "without contacting a device", though open-world also denotes an unbounded data domain, so this is not a hard contradiction.

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 front-loaded sentence with no filler; the scoping fact (no device contact) is placed immediately. It is efficient, though so terse that it borders on under-specified for a four-parameter tool.

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?

With no output schema, 25% parameter coverage and no annotations explaining return shape, the description should say what a paged response looks like and how snapshot_id is sourced. Neither is present, so an agent can tell roughly what the tool does but not confidently how to drive it.

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 only 25% – only analysis_project_id is documented, and that documentation lives in the schema, not the description. The verb "Page" hints that limit/offset are pagination controls, but the required snapshot_id (format, and where to obtain it, e.g. from snapshot_storage) is left entirely unexplained at both layers.

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?

"Page retained local storage snapshot file records" gives a specific verb (paginate/read) and a specific resource, and "without contacting a device" separates it from live-collection siblings such as collect_storage_files and snapshot_storage. It stops short of naming a sibling outright, so it is clear but not fully differentiated.

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 a device" implies the tool is for working against already-retained snapshots rather than pulling fresh data, which is useful implied context. There is no explicit when-to-use/when-not statement and no pointer to collect_storage_files, snapshot_storage or diff_storage as alternatives.

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