step_simulation

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

Discloses that stepping simulation advances by N frames and observes states, which is the core behavior. Lacks mention of potential side effects (e.g., irreversible physics state changes) but is adequate for a simulation stepping tool. No annotations to contradict.

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?

Well-structured with a concise first sentence, then rationale for usage, a debug loop example, and parameter docs. Every sentence adds value without redundancy.

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 3 optional parameters and an output schema, the description covers purpose, usage, parameters, and provides a typical workflow, making it fully sufficient for an AI agent to use correctly.

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?

Description includes an 'Args' section that clearly explains all three parameters (num_steps, observe_prims, observe_joints), adding meaning beyond the input schema which has no 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?

Description uses specific verb 'step' and resource 'simulation', clearly states it's for debugging robot behavior, and distinguishes from siblings like play_simulation and execute_script.

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?

Explicitly recommends using instead of play_simulation + sleep + execute_script, and provides a typical debug loop with numbered steps, giving clear when-to-use guidance.

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