Read bounded Fabric world observation

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

The readOnlyHint annotation already establishes the safety profile, and the description adds real value beyond it: the data is aggregated and 'privacy-safe', contains no player identities, makes no world changes, is bounded to 'recent' data, and covers only one already-loaded chunk. It does not explain what the aggregate sample contains or how 'recent' is bounded, but its scope and exclusion disclosures are substantially stronger than the annotation alone.

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 compact sentence front-loads the operation, then the scope and the privacy constraints; every clause carries information, and none is padding.

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 no-parameter read with no output schema, the description should say more about what the returned aggregate actually contains, because the agent gets no schema to lean on. It is adequate on scope and privacy, but it leaves the response shape and the meaning of 'recent' and 'chunk' implicit.

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 there is nothing for the description to disambiguate; a baseline of 4 applies here. The description does not need to explain any arguments.

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 gives a concrete verb (read) and resource (recent aggregate sample of one already-loaded chunk), which tells an agent what it gets back. It does not distinguish itself from siblings such as guia_status or guia_performance, and since there are no parameters, it never states which chunk or how the chunk is chosen.

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, even though guia_diagnose, guia_status, and guia_performance are plausible substitutes for observation. At most, the phrasing implies one should use this tool to inspect the current loaded chunk.

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