Blender Setup Rigid Body

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

With no annotations, the description must disclose behavioral traits. It only says 'Add...', implying creation, but does not describe what happens if rigid body already exists, error handling, or side effects. Lacks important behavioral context.

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?

Two sentences, front-loaded with purpose. Second sentence about pattern is less relevant but not harmful. Could be slightly more concise, but overall efficient.

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 11 parameters and no output schema or annotations, the description is incomplete. It does not mention return values, error conditions, or that it requires an existing object. Missing critical context for a complex 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%, so baseline is 3. The description mentions type, shape, mass, friction, and damping, which covers some parameters but omits restitution, linearDamping, angularDamping, useMargin, collisionMargin, and timeoutMs. Adds minimal value beyond schema.

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 adds rigid body physics to a Blender object, listing specific settings (type, shape, mass, friction, damping). It distinguishes from sibling Blender physics tools like blender_apply_force and blender_set_gravity.

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 explicit usage guidance provided. Does not specify when to use this tool vs alternatives or prerequisites (e.g., object must exist). The mention of mirroring a pattern is not helpful for deciding when to invoke.

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