overview

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose meaningful field semantics (negative `available` means a penalty, `last_copy` warns selling would lose the happiness bonus, `in_city` determines routability), which is real value. However, it never states that this is a side-effect-free read or mentions any prerequisites, so key behavioral traits remain implicit.

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?

It is front-loaded with a good one-line summary, but the body is a dense run-on paragraph enumerating keys with no grouping or formatting, making it hard to scan. Every clause arguably earns its place as return-value documentation, but the structure wastes the reader's attention.

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 and no annotations, the description is the sole documentation of what comes back, and it covers the top-level fields, breakdowns, and edge-case flags thoroughly. It defers exhaustive key detail to how_to_play, which is a reasonable division of labor, though a couple of fields (e.g. `unit_supply`, `score_breakdown`) are named without explanation.

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?

The tool takes zero parameters, so there is no parameter semantics to document; the baseline of 4 applies. The description instead spends its effort on return-value semantics, which is the right target 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?

The opening clause 'My empire at a glance' with an enumerated list of resources (gold, science, culture, happiness, era, turn) makes clear this is a read snapshot of empire state. It is specific about content but never contrasts itself with siblings like turn_status, demographics, or culture_overview, so an agent gets no help choosing among them.

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 explicit when-to-use or when-not-to-use guidance; the only routing hint is 'Every key in detail: how_to_play("overview")', which points to a documentation sibling rather than stating a selection condition. The agent must infer that this is for periodic status checks.

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