origin_set

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

No annotations provided, so description must disclose effects. It does not mention if the operation is destructive, reversible, affects children, or requires object selection. Only states it sets origin.

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, first states purpose, second lists types. Efficient and front-loaded, but could be slightly more structured with bullet points for types.

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 no annotations and no output schema, the description lacks important context: what happens to the object's location, is it destructive, any undo implications, prerequisites (e.g., object must be selected). Incomplete for a mutation 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?

Parameter 'name' is not described (implied). 'type' is explained with a list of enum values, adding meaning beyond the schema which lacks descriptions. However, schema coverage is 0%, so description should do more.

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 the specific verb 'Set' and resource 'origin point of an object', and lists distinct types. This clearly distinguishes it from sibling tools like 'center_objects' or 'apply_transform'.

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 on when to use this tool vs alternatives (e.g., center_objects, apply_transform). No mention of prerequisites, when to choose one type over another, or when not to use.

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