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

The description goes well beyond annotations by disclosing the liveness-guard acquisition, the Base receipt-checking behavior, the exact field-matching requirement, and the explicit limitations on retries and later steps. This materially informs an agent about side effects and non-effects even though annotations already indicate idempotence and non-destructiveness.

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 description is dense but each sentence carries meaningful information: the workflow, the validation criteria, the behavioral constraints, and the response shape plus auth requirement. It is slightly heavy with jargon like 'permanent process-liveness guard,' but it is well structured and 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?

Given zero parameters, an existing output schema, and rich annotations, the description covers all needed operational context: what it does, what it verifies, what it never does, what it returns, and the required server-to-server auth. Nothing critical for invoking it 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 tool has zero parameters and the schema is empty, so there are no parameter semantics to document. The description adds relevant context by mentioning the x-otto-delegation-auth secret, though this is an auth header rather than a schema parameter.

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?

Title and description name a specific verb ('reconcile') and resource ('one end user's known-hash delegated operation'), then explain the concrete workflow: acquire a liveness guard, check Base for finalized receipts, and validate fields. It also distinguishes itself from siblings by stating it never calls CDP, never retries, and never builds or submits later steps.

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 gives clear context: this is server-to-server only and requires Otto's delegation secret in x-otto-delegation-auth. It also clarifies what it does not do (no retries, no later-step submission, leaves no-hash steps unresolved), but it does not explicitly name an alternative sibling for cases where those behaviors are needed.

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