rhino_camera_set

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

The description implies a state change (positioning camera), which aligns with readOnlyHint=false. However, it does not disclose any behavioral nuances such as whether the change is permanent, how existing camera settings are affected, or if the viewport must be in a specific mode (e.g., perspective). With no annotations providing additional safety hints, the description falls short.

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, front-loaded sentence of 12 words. It efficiently conveys the core action and parameters with no extraneous information.

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 tool's simplicity and the presence of an output schema, the description lacks important context such as coordinate system, presence of error conditions, or prerequisites (e.g., a viewport must exist). It does not mention the optional view_name parameter or how the lens length relates to camera behavior. A mutation tool like this would benefit from more thorough context.

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 description restates parameter names from the schema ('location', 'target', 'lens length') but adds no new meaning. The schema itself has some descriptions for nested Point3dModel fields and bounds for lens_length_mm, but the description does not explain the significance of these parameters (e.g., coordinate system, units, behavior of view_name). Overall added value is minimal.

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 ('Position') and resource ('active viewport's camera'), listing the three components (location, target, lens length). It is specific and unambiguous, but does not explicitly distinguish itself from sibling tools like 'rhino_view_set' or 'rhino_zoom_extent', which also adjust the view.

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 on when to use this tool versus alternatives. Siblings such as 'rhino_view_set' or 'rhino_zoom_object' could serve similar purposes, but the description offers no context for choosing this tool over them.

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