Set Pivot

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

The description 'Set' implies a mutating operation, which aligns with annotations (readOnlyHint=false). Annotations already declare idempotentHint=true and destructiveHint=false, so the description adds no new behavioral context beyond stating the intent.

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?

A single, front-loaded sentence that conveys the essential purpose without extraneous words. Every part earns its place.

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 the presence of annotations and output schema, the description is adequate for this simple operation. However, a brief usage hint (e.g., noting idempotency or relation to center_pivot) would improve completeness slightly.

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%, and the description does not add any meaning beyond what the schema already documents for `node`, `position`, and `world_space`. Baseline 3 is appropriate as the schema fully handles parameter semantics.

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 action ('Set') and the resource ('pivot point of a node') with a specific verb and noun. It implicitly distinguishes from the sibling `modeling.center_pivot` by targeting an explicit position rather than centering.

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 like `modeling.center_pivot` or other pivot-related operations. It does not mention any prerequisites, side effects, or exclusion criteria.

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