Fetch genesis document

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

Annotations cover the safety profile (readOnly, idempotent, non-destructive, openWorld), and the description adds substantive behavior beyond them: return encoding (CBOR, base64), that the bootstrap key is preserved for the verifier, the provenance ('fetched'), and the trust-root caveat about copies taken at check time. This is real context an agent cannot get from the annotations.

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 endpoint is front-loaded, but the body is a dense, semicolon-chained run-on with cryptic boilerplate tags ('Provenance: fetched. Supports: sealing...') that are hard to parse. It is information-rich yet not cleanly structured.

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?

With an output schema and full annotations present, the description still supplies the trust and capture context an agent needs to use the result correctly. Minor gaps remain around the cryptic 'Supports' tag and when a fresh fetch is legitimate.

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 both logId and baseUrl are already documented in the schema; the description only embeds them in the URL template, adding no format or fallback semantics beyond what the schema states. Baseline 3 applies.

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 specific verb (GET) and resource (the forest's genesis document) plus the exact endpoint template, so the agent knows precisely what is retrieved. It is readily distinguishable from siblings like fetch_receipt or fetch_accumulator because it names the genesis document and its chain-binding contents.

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?

Gives concrete usage guidance: 'obtain it once, keep it, and pass it as bytes from then on,' with an explicit when-not ('A copy obtained at check time is not the genesis trust root as intended'). It does not name sibling tools as alternatives, so it stops short of the top band.

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