pro_visualize_camera

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

It usefully discloses that the change is session-level and not persisted ('No save') and that it rewrites the model view rather than creating a camera entity. However, it never warns that applying overwrites the current active view (the destructiveHint the annotations declare), and it does not say what an inspect call yields. Decent added context, but it leaves the mutation risk to the annotations.

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?

Four tight sentences with the core purpose front-loaded, followed by the disambiguation and the direction convention. The telegraphic 'No save.' and 'For custom orientation...' fragments are efficient, though slightly clipped for an agent parsing unfamiliar domain terms.

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 9-parameter, destructive, output-schema-less tool, the definition covers purpose and the custom-orientation convention but omits what an inspect call returns and how fit/zoom_factor/perspective interact with the chosen view. An agent can invoke it, but cannot predict the result of the inspect path.

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 description coverage is only 11%, so the description must carry parameter meaning; it does explain from_direction (points from model toward camera) and up_direction (desired up axis), which the schema leaves bare. It says nothing about action, fit, zoom_factor, perspective, or document_path, so most of the 9 parameters remain unexplained.

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?

States specific verbs (inspect/apply) and a precise resource (the saved model's active view orientation, framing and perspective), and explicitly contrasts it with a named camera entity or lens, which is exactly the sibling pro_visualize_named_camera. An agent can route correctly without opening either schema.

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 inspect-vs-apply split plus the 'not a named camera entity or lens' clause give clear routing context away from pro_visualize_named_camera. It stops short of naming alternatives for the adjacent render/capture siblings (pro_capture_view, pro_visualize_render), so it is clear context without full exclusions.

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