omni_state

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

No annotations are present, so the description carries the full burden. It discloses that this is a non-mutating snapshot and enumerates the data fields returned, which tells an agent what to expect. It could go further on failure modes or side effects, but 'snapshot' suggests pure read and the field list is good.

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 sentences with zero filler. The first sentence states the output contents; the second gives the exact invocation timing. Both earn their place and key guidance is 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?

For a zero-parameter, no-output-schema state query, the description tells the agent exactly when to call it and what fields it will see. It doesn't detail error cases or connection assumptions, but those aren't critical for this simple read-only snapshot tool.

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?

With zero parameters, the schema is trivially 100% covered and the baseline is 4. The description doesn't need to explain parameters; it adds context about what the snapshot contains, which is the relevant semantic guidance here.

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?

Description states a specific verb ('Snapshot') and resource ('running game'), enumerating exactly the contents (status state, screen, mode, player position/health/food, world, devpatch status). This clearly distinguishes it from siblings that perform specific actions like world entry, scanning, or shape creation.

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?

Explicitly tells when to call: 'before EVERY interaction' and why: to confirm the loaded world matches expectations. This provides strong timing guidance, though it doesn't name alternative tools or explicitly state when-not-to-use, so one point is withheld.

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