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

The annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds genuine behavioral detail beyond them: it reveals the data source (a world file) and discloses that the doctor summary is included conditionally, only 'when a report sits next to the world file' — a non-obvious conditional field an agent would otherwise misread as always present.

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?

One compact sentence with the most important content (what world, which fields) front-loaded and no filler. It loses a point for being a bare fragment with no verb and for the slightly convoluted trailing clause about the report sitting next to the world file.

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?

An output schema exists and annotations fully cover safety, so the description needn't explain return values; it nevertheless enumerates the key fields, which is helpful. What is missing for a tool in a crowded status/inspect family is any statement of how it relates to cell_status or docs_status, so an agent knows which one to reach for.

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 the baseline is 4 and there is nothing for the description to disambiguate. The description correctly implies the call is scoped implicitly to the current cell rather than accepting an identifier, which is consistent with the empty schema.

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 is a noun phrase that identifies the resource ('the world this cell lives in') and enumerates its contents (id, chain, network, contracts by id, bundle hash, doctor summary), so an agent can infer it returns the world record for the current cell. However, no verb states the action, and nothing distinguishes it from close siblings such as cell_status or docs_status, leaving the agent to guess at the boundary.

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 guidance and no mention of alternatives. The phrase 'the world this cell lives in' only weakly implies 'call this to learn about your environment', and an agent choosing between this and cell_status or safety_status gets no routing help at all.

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