get_report_snapshot

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

Adds details beyond annotations: immutable JSON, original SHA-256 hash, timestamp, no auth, fully idempotent. Annotations already declare read-only and idempotent, so some redundancy, but the immutable/hash detail adds value.

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?

Two clear sentences, front-loaded with purpose, then details. No fluff, each sentence adds distinct info. Slightly longer than minimal, but concise.

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?

Given simple read operation with good annotations and full schema coverage, description covers behavioral details, usage context, and alternative. Fully complete for this tool.

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 covers both parameters well (snapshotId, format with enum). Description references snapshotId source but adds little beyond schema; no format details beyond what schema provides. Coverage is 100%, so baseline 3.

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?

Purpose is crystal clear: 'Read a previously created IntoDNS.ai Everything Report snapshot by snapshot ID.' It distinguishes from get_everything_report (live data vs snapshot) and specifies the resource (snapshot) and action (read).

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 states when to use (verify/re-read audit trail) and when not to (use get_everything_report for current live data), plus the prerequisite of obtaining snapshotId from create_report_snapshot.

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