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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the output includes census, poles, frame, and chain references, but does not disclose whether the operation is read-only, whether it has side effects, what authorization is needed, or how invalid mesh levels are handled. The ambiguous word 'free' further reduces transparency.

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 description is a single, fairly compact sentence and puts the main object up front. However, it is packed with unexplained domain jargon ('reality', 'census', 'poles', 'frame', 'chain references') and the ambiguous qualifier 'free.' It is not bloated, but it is not maximally clear.

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 single-parameter call, the description gives enough to attempt a default invocation: the slice range is specified and the returned state components are listed. However, there is no output schema, no usage context, no definitions of core terms, and no guidance about when this tool is appropriate relative to its siblings. It is minimally adequate, but with clear gaps.

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 schema has 0% description coverage, but the description meaningfully compensates by explaining that the tool operates at a 'given mesh level (2–7)', which maps directly to the slice parameter. It provides both semantic meaning and an allowed range. It does not reference the parameter by name or mention defaults, but the compensating value is strong for a single-parameter tool.

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 identifies an object ('newest tick of reality') and its contents ('canonical state ... census, poles, frame and chain references'), implying this tool returns the latest canonical state for a given mesh level. However, it lacks a clear verb like 'retrieves' or 'returns', and uses ambiguous language such as 'free.' It does not differentiate itself from sibling tools.

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 guidance on when to use this tool versus alternatives like bid, catalog, ground, or rent_roll. The phrase 'canonical state' hints at authoritative current data, but this is implied rather than stated. No exclusions, alternatives, or selection criteria are provided.

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