omni_world_raycast

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

With no annotations provided, the description carries the full disclosure burden. It usefully reveals the origin fallback ('or player eye') and the return contract, but it omits no-hit behavior, whether the ray stops at the first block, coordinate space, and what counts as an entity — material edge cases for reliable invocation.

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?

Two tigh sentences, with the core action in the first and the return contract in the second. No fluff; every phrase carries 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?

For a four-parameter tool with no output schema and no annotations, the description covers the happy-path call adequately but leaves edge/failure behavior and parameter formatting to inference. It is minimally viable, not complete.

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 0%, so the description must add meaning. It clarifies origin ('or player eye' implies an optional/default origin), direction ('along direction'), and distance (ray length), and implicitly ties entity hits to includeEntities; however, it leaves units, coordinate format, and direction normalization unstated.

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?

The description names a specific action — 'Raycast from origin (or player eye) along direction' — and enumerates the return payload: block hit, face, distance, and entity hit. This is a distinctive, resource-bound description that an agent can separate from sibling tools like omni_world_scan, though it never names alternatives.

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?

There is no statement of when to use this tool versus omni_world_scan, omni_block_search, or the other world tools, and no exclusions or prerequisites are given. An agent must infer that the tool is meant for line-of-sight probing, which is risky given the large sibling set.

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