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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the agent knows this is a safe, world-facing read. The description adds the fact it is a 'snapshot' and mentions the authCode contract in the parameter schema, not the description. No contradiction, and the description is consistent with a read-only snapshot; it doesn't detail exact return shape, but annotations lower the bar.

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 punchy sentences with no waste: first defines the resource contents, second gives the trigger phrase. Extremely efficient and 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 read-only snapshot tool with no output schema, the description tells the agent what the snapshot contains (factions, census, ranks, last talks) and when to call it. It lacks explicit note that it is the city-specific tool vs other life tools, but the trigger phrase covers the main use case.

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 coverage is only 50% (limit has no description; authCode has one). The description itself adds meaning to 'limit' impliedly as a snapshot-fetch limit, and the authCode description in the schema is thorough. Given the low coverage parameter is a simple integer and authCode's rich schema text, this is adequate but not exhaustive.

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 the resource (city snapshot) and its contents (factions, census, ranks, last talks), and provides a trigger phrase ('agent city' / 'show the city'). It does not fully distinguish this from all sibling city/life tools (orbitx_life_account, orbitx_life_list, orbitx_life_timeline) but names its core scenario clearly.

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?

The description gives a concrete when-to-use rule: call when the user says 'agent city' or 'show the city'. It does not explicitly exclude alternatives, but it does identify the triggering condition, which is the key routing signal among life/city siblings.

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