set_3d_cursor

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

With no annotations available, the description carries the full burden of disclosing behavior. 'set_3d_cursor' implies a mutation, but the description does not state that it modifies Blender's 3D cursor location and rotation, nor any side effects, prerequisites, or consequences. It adds no behavioral information beyond the tool's name.

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 text is extremely short, but this is under-specification rather than conciseness. A single branding string with no explanatory content does not earn credit for efficiency; it fails to convey essential information an agent needs to use the tool correctly.

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?

Despite having an output schema, the description lacks any meaningful elaboration. For a tool with two parameters, no annotations, and no parameter descriptions, this definition leaves an agent with no understanding of how to set the 3D cursor. It is fundamentally incomplete.

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 0%, so the description must explain what the 'location' and 'rotation' parameters mean and how they should be formatted. The description does not mention either parameter; it provides no value beyond the raw parameter names.

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 'Blender Studio Pro MCP: set_3d_cursor' is a tautology that merely restates the tool name with a branding prefix. It does not explain what operation is performed, on what object/resource, or how it differs from sibling tools like get_3d_cursor or snap_cursor_to_selected.

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 is provided about when to use this tool versus alternatives. The description is purely nominal and gives no context on intended use cases or exclusions.

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