rhino_named_view_save

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

The description only states the basic action. It does not disclose side effects like overwriting existing views, permanence, or any required view state. Annotations indicate readOnlyHint=false which aligns with 'save', but no additional behavioral context is provided.

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, clear sentence with no fluff. It is front-loaded and efficient, though it could be slightly expanded to include parameter hints without losing conciseness.

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 simple save operation with two parameters, the description is minimally adequate but lacks mention of optional doc_id, overwrite behavior, or prerequisites. Given annotations and output schema presence, more detail would improve completeness.

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 does not explain any parameters. The input schema provides some info (name required, doc_id optional with a description), but the tool description adds zero value beyond that. With 0% schema description coverage (as per context), the burden on the description is higher, and it fails to compensate.

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: save current camera as a named view. It uses a specific verb and resource, but does not explicitly distinguish from sibling view tools like rhino_view_set or rhino_zoom_extent, though the distinct purpose is implied.

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 versus alternatives. There is no mention of prerequisites, context, or when not to use it.

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