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

Adds substantial behavior beyond the readOnlyHint/openWorldHint/idempotentHint annotations: the fail-closed unresolved flag semantics, exclusion of stored serialized transactions and idempotency keys, no submission/retry guarantee, and the required x-otto-delegation-auth header with server-to-server constraint. This is exactly the kind of context that changes how an agent should interpret results.

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?

Dense but every sentence earns its place: the first sentence defines scope, the second explains optional filtering and result shape, the third clarifies fail-closed semantics, and the fourth covers security and exclusions. No redundant restatement of the title or schema; the length is justified by the operational and security nuances.

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 zero-parameter read tool with an output schema and rich annotations, the description is complete. It covers auth requirements, result scope, failure semantics, data-privacy exclusions, and the no-mutation guarantee. Nothing an agent needs to invoke this correctly is missing.

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 schema declares zero explicit parameters, which sets a baseline of 4. The description further clarifies that accessToken resolves the end user and that artifactId is an optional selector with meaningful behavioral consequences (exact operation versus history plus unresolved operations). This is valuable semantic context about parameters that live outside the JSON schema.

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 ('Read') with a precise resource ('durable Base delegated-operation journal') and the owning entity. The title reinforces 'history and recovery state,' and the description explicitly excludes submission/retry behavior, making it clearly distinguishable from sibling tools like otto_submit_under_delegation and otto_delegation_reconcile.

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 makes the read-only, server-to-server intent explicit and explains the effect of including artifactId versus omitting it. It does not name specific sibling alternatives or state 'use this instead of X,' but the behavioral boundaries (never submits, never retries, requires delegation auth, no userId) give an agent enough context to select this over mutation or status tools.

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