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

With no annotations the description carries the full burden and does disclose auth (credential: key), cost and throttling (Free, 20 exports/hour), a side-effect guarantee ('Original receipts remain unchanged'), a version-dependent signing behavior (format v2 signs document, snapshot and every entry field when a notary key is configured), and an explicit scope caveat that it authenticates the Court's assertions rather than source records or compliance. It stops short of saying whether the call is read-only in effect or what failure modes exist.

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?

Metadata is packed efficiently at the end ('Credential: key. Cost: Free; 20 exports an hour. Source: PD8 §4, §8.'), but the opening sentence is written from the requester's viewpoint and largely duplicates the purpose already given in the next sentence. The middle is dense and the caveat about Court assertions vs. source records is buried rather than front-loaded.

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 no-parameter, no-annotations tool with no output schema, the description covers the important ground: auth, rate limit, signing/format behavior, non-destructiveness of receipts, unavailable legacy originals, and the limits of what the authentication proves. The gap is that with no output schema it never characterizes the shape of the returned snapshot beyond 'one database snapshot'.

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?

The tool takes zero parameters, so there is nothing for the description to clarify and the baseline of 4 applies. The schema is an empty object and coverage is 100%, so no compensating detail is required.

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 second sentence gives a clear verb+resource: it 'Returns all of your own lodgements visible in one database snapshot,' which tells an agent this produces a scoped export. The odd first-person opener ('I need an authenticated snapshot...') muddies it slightly, and it never distinguishes itself from close siblings like read_register, my_register, request_register or check_record.

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?

There is no when-to-use statement and no alternative tool is named, despite the crowded register/hold/check sibling cluster. The only actionable direction ('Verify against an independently trusted key') concerns post-export verification of the artifact, not selection of this tool over its neighbors.

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