get-world-info

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

The description lacks detail on what 'basic information' includes, such as system rules, world settings, or module data. No annotations exist, so the description must convey safety and behavior—it does not. It only says 'get', implying read-only, but no confirmation.

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 sentence that front-loads the purpose. It is concise but could be slightly more informative without being wordy. It earns its place but is on the lean side.

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?

Given no output schema, the description should explain what 'basic information' includes. It is vague. For a tool with zero parameters and a generic purpose, this is minimally adequate but not complete—leaves agent guessing about return content.

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?

There are no parameters, and the schema coverage is 100%, so the description need not add parameter details. The baseline for 0 parameters is 4; the description adds no further info, which is acceptable.

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 clearly states the verb 'Get' and the resource 'basic information about the Foundry world and system'. It distinguishes from sibling tools like get-actor or get-scene-dimensions by targeting world/system info.

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?

No guidance is provided on when to use this tool versus alternatives. There is no explicit mention of scenarios, prerequisites, or when not to use it. With many sibling getter tools, this omission hinders agent decision-making.

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