get_simulation_info

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

With no annotations, the description carries the behavioral burden and does so well: it explains cache fallback behavior, the `note` caveat, the no-geometry case, implicit simulation when the scene is ahead, Houdini's interrupt dialog and lack of deadline, and the `interrupted` flag. This is unusually transparent about side effects and edge cases.

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 front-loaded with the purpose and every paragraph adds relevant caveats about simulation/cache behavior. It is somewhat dense and could be structured more cleanly, but there is little wasted text for a behaviorally complex tool.

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 and no annotations, the description is fairly complete: it explains the main returned state (`simulation_frame`), the `note` fallback, and `interrupted`. It still does not fully describe the response shape or route the agent away from sibling DOP tools, leaving minor contextual gaps.

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%, so the description must compensate for the single `node_path` parameter. It identifies it as a DOP network node path, which is useful, but gives no path format, example, or guidance on discovering valid DOP networks.

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 states a specific verb and resource: getting DOP network simulation state at the current frame. It clearly scopes the result to simulation state, not generic node info, but it does not explicitly distinguish itself from sibling DOP inspection tools such as get_dop_object or list_dop_objects.

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 gives a clear usage condition: check this before measuring or rendering a frame reached backwards. It does not name alternatives or exclusions, such as when to use step_simulation or get_dop_object instead, so it falls short of explicit when/when-not guidance.

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