get_simulation_info

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses almost nothing. It does not say whether the call mutates anything, whether the simulation must already be running, whether it is safe to call repeatedly, or what the returned 'state' contains.

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 content is front-loaded in a single sentence with the argument note following, and nothing is redundant. The 'Args:' block is boilerplate but costs little, and the whole definition is appropriately terse for a one-parameter getter.

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?

With no output schema, no annotations, and 0% schema description coverage, the description needs to do more work than it does. An agent still cannot tell what the returned simulation state includes, whether prior setup is required, or how this differs from the other DOP inspection tools.

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. It does add one meaningful qualifier to node_path — that the path must refer to a DOP network node — which is not present in the schema. Beyond that single hint, it adds no format, syntax, or validation detail for the parameter.

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 ('Get DOP network simulation state'), so an agent knows it is a read operation scoped to a DOP network. It does not, however, differentiate itself from siblings that also read DOP data (get_dop_object, get_dop_field, get_dop_relationships, get_sim_memory_usage), nor does it clarify what 'state' comprises.

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?

There is no guidance on when to call this versus the many neighbouring DOP tools (list_dop_objects, get_dop_object, get_dop_field, step_simulation, reset_simulation). No prerequisites, no exclusions, no conditions for use are stated.

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