World & entities

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

No annotations provided, so the description carries full burden for behavioral disclosure. It fails to state that the tool is read-only, lacks information on permissions, side effects, or response size. The list of returned stats is helpful but insufficient for safety or performance awareness.

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?

Single concise sentence that efficiently lists all included statistics. No redundant words, every phrase adds value.

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 simple stats retrieval tool with no output schema, the description sufficiently outlines the returned data categories. However, it could mention the format (e.g., JSON) or whether results are nested, though not strictly required given the explicit list.

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 100%, so baseline is 3. The description does not add any parameter meaning beyond what the schema already provides (e.g., topN is implied by 'top entity types' but schema already describes it). No added semantic value.

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?

Description clearly states 'World/entity statistics' and lists specific data points (total entities, top entity types, per-world totals, data packs, non-default game rules), making the verb-resource relationship explicit and distinguishing it from sibling tools like get_summary.

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 implies usage for retrieving world/entity statistics but provides no explicit guidance on when to use this tool over alternatives or when not to use it. Agent can infer context from the listed data items, but exclusions are absent.

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