get_report_snapshot

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds value beyond these by disclosing the immutable JSON nature, SHA-256 content hash, timestamp inclusion, and the fact that no auth is required — a meaningful behavioral guarantee for audit scenarios. Credit is given for adding context that the annotations themselves don't capture, though the safety profile was already covered by the structured data.

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 sentences, front-loaded with the core purpose, using an em-dash and semicolon for efficient packing of information. Every clause contributes: what it does, what it returns, its key properties (read-only, hash, timestamp), and when to use an alternative. Zero fluff.

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 simple 2-parameter tool with 1 required param and no output schema (JSON return must be self-contained), the description covers all critical aspects: purpose, return behavior, authentication state, immutability, and relationship to the sibling tool. No important context is missing given the tool's complexity.

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 3 applies. The description adds provenance for snapshotId ('Requires snapshotId from create_report_snapshot') but doesn't add syntax, format, or semantic details beyond what the schema's property descriptions already provide. This is adequate but not exemplary.

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+resource combination ('Read a previously created IntoDNS.ai Everything Report evidence snapshot by snapshot ID'), names the exact partner tool (create_report_snapshot), and explicitly distinguishes itself from get_everything_report. It leaves no ambiguity about what this tool does.

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 description provides an explicit when-to-use scenario ('Use to verify or re-read an audit-trail evidence record without re-running a live scan') and an explicit alternative with a clear exclusion ('use get_everything_report for current live data instead'). It names the sibling tool directly, making the choice unambiguous.

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