omni_world_scan

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

With no annotations, the description carries the full burden and it discloses two crucial behaviors: the 262,144-block hard cap and truncation to maxBlocks/maxEntities. It doesn't cover error cases or filter interplay but is fairly transparent for a read-only snapshot.

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?

Three short sentences with purpose first; every phrase earns its place. Slight redundancy between 64^3 and 262,144 does not hurt.

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 and no annotations mean the description should cover return value shape and invocation semantics. It leaves coordinate conventions and filter syntax unexplained, so an agent cannot reliably invoke it correctly.

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 has 0% parameter descriptions, so the description must explain them. It only relates maxBlocks/maxEntities to truncation and implies from/to define the box; blockFilter, includeBlocks, and includeEntities are left unexplained.

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 concrete operation — capturing a block/entity snapshot in a bounded 64^3 box — and adds hard limits. It doesn't explicitly distinguish siblings like omni_world_raycast, but the boxed-snapshot scope is clear.

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?

No explicit when-to-use or alternative exclusions; the only guidance is the implied use case of snapshotting a bounded volume. Given related sibling tools, an agent gets no explicit route to choose this over a raycast or block search.

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