snapshot_detail

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

No annotations, so the description must carry behavior; it usefully discloses that the underlying snapshot was shortened, which tells the agent the data it retrieves may be truncated. It implies a read operation but doesn't state what happens when ref/query match nothing, leaving one gap for a no-annotation 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?

Three tight sentences, front-loaded with the core purpose, then parameter routing, then the usage hint. No filler; every clause carries information the agent needs.

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 read-only retrieval tool with all three parameters documented in the schema and no output schema, the description covers purpose, parameter meaning, and the alternative tool. A note on return shape or empty-match behavior would fully close it, but it is otherwise complete.

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 is 100%, so baseline is 3, but the description adds real meaning: it gives ref format examples (e123, 1_45) and explains that ref returns 'that element and everything inside it' while query returns text 'with its surrounding section.' Only max_chars is left to the schema.

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 (Read) on a specific resource (part of the last page snapshot), and clarifies that the snapshot was shortened by tokensave-mcp-diet. This distinguishes it sharply from browser_snapshot and other siblings by making the 'partial/truncated retrieval' role explicit.

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?

Explicitly says 'Use this instead of taking a new full snapshot,' naming the alternative behavior (full snapshot). It also gives per-parameter when-to-use conditions (ref for element subtree, query for text lookup). It doesn't state a when-not case beyond that, but the routing is clear.

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