slide_get_snapshot

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

No annotations are provided, so the description must carry the behavioral disclosure burden. It does clarify the read-only nature ('Get') and the output scope ('storage locations and any deletions'). Still, it does not mention error behavior, authorization requirements, or whether 'deletions' means soft-deleted entries, destructive history, or something else.

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?

The description is a single sentence with no wasted words. The core lookup semantics are front-loaded, and the return details follow naturally. Every part contributes to the reader's understanding.

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-parameter get operation with no output schema, the description gives a reasonable overview of what is returned. It is mostly complete for invocation purposes. It could be more complete by describing the response shape or not-found behavior, but the core behavior and return scope are clear enough.

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 100%, so the baseline is 3 even without additional parameter explanation. The description adds no meaning beyond what the schema already states—it just confirms the operation keys off snapshot_id. No format, examples, or constraints are provided.

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?

The description uses a specific verb and resource: 'Get a single snapshot by ID.' It also tells us what the response contains ('its storage locations and any deletions'), which distinguishes it from listing endpoints like slide_list_snapshots and from verification-specific endpoints like slide_get_snapshot_service_verification.

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 'by ID' phrasing implies this is for a direct lookup rather than a list or search, so the intended use is somewhat clear. However, it does not explicitly state when to choose this over slide_list_snapshots, nor does it mention any alternatives or exclusions.

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