generate_scene

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

With no annotations, the description carries the burden. It discloses two important behavioral traits: it consumes real LLM budget (bounded) and takes minutes. However, it doesn't mention whether the scene is persisted, whether a session is created, or any side effects on existing state, leaving partial transparency.

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?

Two sentences: the first identifies the purpose, the second adds critical cost/time caveats. Every word earns its place, and the most important information is front-loaded.

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 has an output schema, return values are covered elsewhere. The description explains the pipeline, budget, and duration, which are essential contextual warnings. It could mention how this relates to sessions (since siblings manage sessions), but overall it is reasonably complete for a generation action.

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 description coverage is 0%, and the description provides no explanation of 'prompt' or 'scene_type'. It merely says 'from a prompt,' but does not elaborate on prompt format, required content, or how scene_type affects output. The description does not compensate for the schema's lack of descriptions.

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 opens with 'Generate a sim-ready Isaac USD scene from a prompt,' which uses a specific verb and resource, clearly distinguishing this tool from siblings like list_categories or get_session_report that handle retrieval rather than creation.

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?

It states the high cost and long duration ('spends real LLM budget... takes minutes'), giving clear context that this is a heavy operation. It does not explicitly name alternatives or exclusions, but the cost/time warning strongly implies use only when a full scene is needed.

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