rhino_origin_set

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

Discloses the behavioral difference between modes (metadata vs. full translation), and notes that reference mode is less disruptive. Annotations indicate readOnlyHint=false, and description adds no contradictions.

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 clear, front-loaded sentences. Efficiently explains the main purpose and both modes without extraneous text.

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?

Output schema exists, and description covers all necessary behavior for a simple tool. Provides sufficient context for correct invocation.

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 already provides detailed parameter descriptions (e.g., mode's two options). The description adds little beyond rephrasing those options, so it does not significantly enhance understanding beyond 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?

Clearly states 'Set the model base point' with two explicit modes. Distinguishes from sibling tools that perform other transformations (e.g., move, rotate) by focusing specifically on origin setting.

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?

Describes when to use each mode: 'reference' for metadata-only geo-referencing, 'translate' for shifting geometry. Provides clear usage context without explicitly stating exclusions.

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