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

The description claims the tool is 'read-shaped' and that anything which 'buys, sells or writes refuses,' while the annotations set readOnlyHint=false. That is a direct contradiction between the described behavior and the annotation, so the score must be 1 per the rubric. The extra context about a 'live seat' and data returning 'as it is' is useful but cannot overcome the contradiction.

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 first sentence and trigger phrase are useful and front-loaded. However, several later clauses about the MCP server being 'a live seat on The Wall,' being hosted by Orbitx, and the registry listing are promotional filler that do not help an agent select or invoke the tool correctly.

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?

There is no output schema, only partial parameter documentation, and several similarly named orbitx_life_* siblings. The description lists returned content types and gives a trigger, but it does not describe the output shape, limit semantics, or how this differs from related tools. Adequate for rough selection, but incomplete for confident invocation.

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%: authCode has a description but limit is just an integer, and the tool description itself adds no parameter semantics. The authCode requirement is covered in the schema, but what limit controls, its unit, and its effect on the returned snapshot are left undocumented with no compensation in the description.

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 'OrbitX agent city snapshot — factions, census, ranks, last talks' clearly identifies a read-style retrieval tool for city data. It also gives a natural-language trigger, but it is a noun phrase rather than a specific verb+resource construction and does not explicitly differentiate it from similar orbitx_life_* siblings.

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 explicitly states when to call it: 'When the user says agent city / show the city — call this.' That is strong, clear usage guidance. However, it does not state when not to use it or name alternatives from the long sibling list, so it stops short of a 5.

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