relationship

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

With no annotations, the description carries the full burden. It discloses the scope and content of the returned data (good behavioral context about what you'll see), but never states that the operation is read-only, requires no permissions, or what happens for unmet civs — leaving the safety/mutation profile to inference.

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?

A single dense paragraph that front-loads the primary content ('our standing with one civ or city-state') before listing specifics. No filler, though the mid-paragraph jump to `discussion()` is slightly jarring.

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 description rightly describes the return payload in detail and even covers the `discuss` button list. The remaining gap is the completely undocumented player_id, but the return-value side is well covered.

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?

There is one parameter (player_id) with 0% schema description coverage, and the description never names or explains it. 'One civ or city-state' implies the target is selected, but the agent gets no confirmation that player_id is the selector or what values it accepts.

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 clearly identifies a read of diplomatic standing with a specific civ or city-state and enumerates the data returned (friendship, denouncements, embassies, opinion lines, PR status, recent messages). It partially distinguishes itself from the sibling `discussion`/`discussion()` tools, though the core verb ('get/view our standing') is implied rather than stated.

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 usage cue — 'call it directly before proposing or answering anything' — and links to `discussion()`, but the referent of 'it' is ambiguous and no when-not-to-use guidance or clear alternative selection is provided. The routing intent is implied rather than explicit.

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