Roblox Simulate Physics

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

Discloses that impulse is instantaneous and force is continuous via VectorForce, but fails to mention side effects (e.g., unanchoring part, overriding existing forces), error conditions, or return value. No annotations to supplement, so 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?

A single, front-loaded sentence with no redundant information. Efficiently conveys the core action.

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 and no annotations, the description should cover overall behavior, state changes, and typical usage. It omits prerequisites, how to choose among impulse/force/torque, and the effect of atPosition. Incomplete for a 6-parameter tool.

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 coverage is 100%, and description adds no new semantic beyond the schema's own parameter descriptions. Baseline 3 is appropriate as schema does the heavy lifting.

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 clearly states the action ('apply an impulse or force') and the target resource ('a BasePart'). It distinguishes from sibling tools like roblox_set_physics or roblox_add_constraint by focusing on direct physics interactions.

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?

No guidance on when to use impulse vs force, prerequisites (e.g., part must not be anchored, physics must be enabled), or alternatives. Lacks explicit when-to-use and when-not-to-use context.

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