scene-enable-arcade-physics-body

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

The description discloses that the tool creates the body and that subsequent property setting is separate. However, it lacks details on error handling (e.g., if body already exists), required physics world state, or return value. No annotations are present to compensate.

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 two concise sentences with no superfluous information. Every sentence earns its place, and it is front-loaded with 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?

Given no output schema and no annotations, the description is insufficient. It omits critical details like how game object IDs are obtained, what happens if a body already exists, prerequisites, and return behavior. The hint about setting properties is helpful but not enough.

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 description adds no information about the two required parameters (sceneId and updates). With schema description coverage at 50% (only sceneId has a description), the description does not compensate by explaining how to find sceneId or what the updates array requires.

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 'Adds an Arcade physics body to the given game objects.' This is a specific verb+resource, and it distinguishes the tool from its sibling 'scene-disable-arcade-physics-body' which removes the body.

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?

The description implies usage by noting that to set properties, you first create the body with this tool. However, it does not explicitly state when to use it vs. alternatives, nor does it mention prerequisites like scene activity or existing game objects.

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