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

Beyond the readOnlyHint/openWorldHint annotations, it discloses substantive traits: no text is generated, output is deterministic for a given input and 'at', results carry a receipt hash, and it states the pricing model ($0.02 USDC per call after 25 free/day). Those cost and determinism facts are exactly the kind of behavior an agent can't 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?

The core purpose is front-loaded, but the body is a dense, comma-chained enumeration ('meanings, story catalyst, imagery, inspiration prompt, story function and archetype, spread templates...') that reads as a payload dump. Every element is arguably relevant, yet the single sprawling sentence makes it harder to scan than a short list would.

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?

With no output schema, the enumeration of return components (spatial card fields, moment card, neighbours, celestial data, narrative seed) does the job of describing the response shape. Combined with 100% param coverage and annotations covering safety, an agent has enough to call it correctly; only the exact response structure/allocation remains implicit.

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 100%, so every parameter (including 'at', 'clock', and _payment) is already documented, making 3 the baseline. The description only reinforces the role of 'at' via the determinism remark and does not clarify 'clock' semantics or the coordinate/timezone fallback behavior 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?

The description states a specific outcome — grounding a scene/NPC/quest in a real place and moment — and enumerates the concrete payload (spatial identity tile card, time portal moment card, eight neighbours, sun altitude/moon phase, narrative seed). It implicitly distinguishes itself from spatial_identity and time_portal by describing itself as the one-call aggregate of both, though it never names those siblings explicitly.

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?

It gives a clear usage context ('ground a scene, NPC, quest or prompt') and signals preference over multiple calls ('in one call'), but it never names the alternative single-purpose tools (spatial_identity, time_portal) or states when a cheaper single-component lookup would suffice. Usage is implied rather than routed.

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