Blender Set Gravity

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

No annotations are provided, so the description must carry the burden. It only states the action and default, failing to disclose side effects (e.g., persistence, physics enablement) or whether it is a safe operation. The description adds no behavioral context beyond the schema.

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 a single, efficient sentence that conveys the essential information. No wasted words or redundant content. It is front-loaded with the action and resource.

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?

For a simple setter tool, the description covers the basic purpose and defaults. However, it lacks usage guidelines and behavioral details, leaving some gaps. Given the tool's simplicity and the presence of sibling tools, it is adequate but not complete.

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?

Parameter schema coverage is 100%, so the baseline is 3. The description adds no additional meaning beyond the schema; it only restates the default. It does not explain the coordinate system (e.g., z is vertical) or the meaning of the components, which are minimally described in the 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 sets the scene gravity vector in Blender, with a verb and resource. It provides the default value, which adds clarity. However, it could better distinguish from other scene-modification tools like blender_set_transform or blender_apply_force, though the specificity of 'gravity vector' helps.

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 provides no guidance on when to use this tool versus alternatives (e.g., blender_apply_force, blender_bake_physics). It does not mention prerequisites such as a valid scene or physics settings. The agent is left to infer context without explicit use cases.

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