getSimulationStatus

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

With no annotations, the description carries the behavioral disclosure burden. 'Query' clearly implies a read-only operation with no side effects, and the enumerated fields fully describe what the caller will observe. It could add edge-case behavior, but for a zero-parameter status query this is a minor gap.

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?

One compact sentence that front-loads the operation ('Query the current simulation state') and lists the relevant output dimensions. There is no filler, repetition, or vague language.

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 no parameters, no annotations, and no output schema, the description provides the core information an agent needs: it clearly identifies a read-only status query and the fields it returns. Adding an example return shape or describing behavior when no simulation is active would make it fully complete, but the current definition is adequate.

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?

The tool takes zero parameters, so there is no schema information needing enrichment. The description avoids inventing unneeded parameter details and instead clarifies the meaningful return fields, which is appropriate at the baseline level.

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 uses a clear query verb and resource ('simulation state') and enumerates exactly what is returned: mode, elapsed time, PDU frame count, and current frame index. This makes it easy to distinguish from sibling tools like getPduResults or getCommandLog.

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 tool versus getNetwork, getDeviceInfo, or getPduResults. The context makes the general purpose obvious, but no explicit when-to-use or alternative-routing guidance is provided.

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