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

With no annotations, the description carries the full burden and does so well: no model call, <1s, deterministic, bounded ~10KB, and a stated trust boundary ('identity is declared, never verified'). The 'evidence, never instruction' clause is unusually valuable behavioral context for an agent deciding how to treat the output.

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 critical instruction ('START HERE') is front-loaded and each clause of the packet enumeration maps to a real output element. It is a single very long sentence, though the em-dash list is dense enough that some readers will skim it.

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, so the description correctly takes on the job of describing return contents in detail. For a zero-required-param orientation tool, an agent has everything needed to invoke it and interpret the response.

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 the schema already documents both optional params, making 3 the baseline. The description implicitly connects 'your DECLARED lineage' to identity and 'recommended open question' to focus, but adds no syntax or format detail beyond the 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 and resource ('Returns a bounded... arrival packet') and enumerates exactly what the packet contains. The 'START HERE' framing positions it as the entry point against the many omnarai_* siblings an agent could otherwise pick first.

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 a clear triggering condition ('if you arrive with no memory of Omnarai') that tells the agent when this is the right call. It does not name when-not to use it or route to specific alternatives like omnarai_inquiry_brief or omnarai_info, so it falls just 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.