Blender Apply Force

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

With no annotations, the description carries full burden. It states the action but does not disclose side effects, whether it modifies existing velocities, if it sets keyframes, or requires the object to already have a rigid body. The behavior is only partially explained.

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?

Single sentence, front-loaded with action and object. Efficient and clear. However, could be slightly more structured with separate clauses for velocity and force field approaches.

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 6 parameters, nested objects, and no output schema, the description is incomplete. It doesn't explain the interplay between parameters, the default behavior when forceFieldType is omitted, or what happens after application (e.g., simulation result). The timeout parameter's relevance is not mentioned.

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 100%, so the baseline is 3. The description does not add significant insight beyond summarizing that linear/angular velocity and force fields are options. It doesn't clarify the relationship between velocity and force field parameters.

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 tool applies initial velocity or force field to a rigid body. It mentions the mechanisms (keyframe velocities, force fields). However, it does not explicitly differentiate from sibling tools like blender_setup_rigid_body or blender_bake_physics, though the purpose is distinct enough.

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 this tool versus alternatives (e.g., blender_setup_rigid_body for setting up rigid bodies, blender_bake_physics for baking). No mention of prerequisites or situations where this tool is inappropriate.

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