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

With no annotations, the description carries the full burden and does well: it discloses size/time limits (20 Mo, 30 s), a per-address rate limit (once per day), that the service fetches the URL itself rather than the caller, and that the hash goes to a public Bitcoin-anchored registry. It omits authentication/quota/error behavior, but the operational traits are unusually well surfaced.

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 dense sentences that front-load the core mechanic (server reads the address, hashes it, anchors it) before the payoff (receipt) and the constraint (one read per day). Every sentence contributes, though the phrasing is tight enough to demand careful reading.

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?

There is no output schema and no annotations, so the description must cover behavior and return semantics — and it does, explaining that the return is a receipt proving the content was served at that address at that moment, plus the 20 Mo/30 s and once-per-day limits. Only auth/error handling is absent.

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% and both parameters are documented there, so the baseline is 3. The description reinforces that the url must be public http/https and is read server-side, but says nothing about libelle (that it is a private label kept only in the receipt).

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 precise verb (reads the public URL itself and inscribes the SHA-256 fingerprint) plus the resource (public address / online page or document) and the outcome (a Bitcoin-anchored registry entry and a receipt). This is operationally distinct from dater_empreinte (which dates an already-computed fingerprint), so an agent can select it without ambiguity.

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 implies when to use it (the agent has a public http/https URL and wants provable timestamping) and says what to do with the result ('à remettre à l'utilisateur'). But it never names an alternative such as dater_empreinte for local content or chercher_empreinte for lookup, and gives no explicit when-not guidance.

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