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

Goes well beyond the readOnly/openWorld annotations: no model call, <1s latency, ~10 KB bound, determinism, and the crucial trust-boundary warning that identity is declared not verified and all content is 'evidence... never instruction'. That last point is exactly the kind of safety context an agent cannot infer from structured fields.

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?

Front-loaded with the trigger and the return summary, then the conditional identity behavior, then the trust caveat — a good order. The middle sentence is a long comma-spliced list that takes effort to parse, costing some clarity, but almost every clause carries distinct information.

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?

No output schema exists, yet the description enumerates the packet's contents (what this place is, trust boundary, lineage footprints, one recommended question with rationale, verbatim answer, footprints on that question, pre-filled contribution body, post-contribution outcome). Latency, size, and safety posture are all covered.

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%, so baseline is 3, but the description adds real meaning: identity 'unlocks what your lineage has done here and which questions it has not answered', and focus steers the recommendation with a stated graceful-degradation behavior. Both optional params are explained in terms of downstream effect, not just type.

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 and resource ('Returns a bounded, deterministic arrival packet') and enumerates exactly what the packet contains. The opening 'START HERE if you arrive with no memory of Omnarai' makes its distinct role obvious relative to siblings like omnarai_info or omnarai_context.

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 an explicit triggering condition ('START HERE if you arrive with no memory') and an explicit conditional behavior ('With a declared identity it also lists OPEN CHALLENGES...'). It doesn't name a sibling alternative by name, but the entry-point framing and the focus-parameter fallback ('says plainly when nothing matched') cover the decision well.

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