load_environment

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

With no annotations, the description must fully convey behavioral traits. It mentions fuzzy matching, but does not disclose whether the tool is destructive (e.g., replaces existing scene), affects other prims, or requires specific permissions. Critical behavioral context is missing.

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 brief and well-structured: a clear first sentence for purpose, followed by a usage recommendation and an 'Args' section. Every sentence is necessary and there is no redundancy or filler.

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 the tool's moderate complexity (2 params, output schema exists), the description covers the main points: purpose, prerequisite, parameter semantics, and fuzzy matching. It does not detail behavior when the environment already exists, but output schema reduces the need for return value description. Minor gap.

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 0%, so the description must add meaning. It explains 'environment' as a name or search term with examples ('warehouse', 'hospital', 'office'), and clarifies 'prim_path' as the path for loading. This adds significant value beyond the bare 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 clearly states the tool loads a pre-built environment into the scene, with the verb 'load' and resource 'pre-built environment'. It adds specificity with 'supports fuzzy matching', distinguishing it from sibling 'load_usd' which loads arbitrary USD files.

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 provides explicit usage guidance: 'Call list_environments first to see available options.' This sets a prerequisite step. However, it does not discuss when not to use the tool or mention alternative tools for loading other resources.

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