set_slice_pivot

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

No annotations are provided, so the description must carry full behavioral disclosure. It only conveys that a property is being written; it does not explain coordinate frame, persistence, errors for missing slices, or effects on rendering.

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 clear sentence with no filler words. However, it is so sparse that brevity comes at the cost of omitting necessary context.

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 mutating tool with no annotations and no output schema, this description omits prerequisites, coordinate semantics, and the distinction from set_slice_center. An agent cannot safely call it without guessing.

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 input schema has four required parameters with 0% schema description coverage, and the description never explicitly mentions x, y, name, or filename. The phrase 'pivot point' hints that x and y are coordinates, but coordinate space, units, and how name/filename select the slice are left unspecified.

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 states a specific verb and resource: 'set' a slice's 'pivot point'. It is clear and understandable, though it does not differentiate itself from the related sibling tool set_slice_center.

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 given about when this tool should be used versus alternatives like set_slice_center or create_slice. It also does not mention that the slice must already exist or how filename/name identify the target.

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