rhino_materials_manager

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

No annotations are provided, so the description must carry the behavioral disclosure burden. The verb 'Open' implies a non-destructive UI action, but the description does not explicitly mention side effects, whether a document must be open, or whether the panel is toggled or focused. Acceptable for a trivial panel opener, but thin.

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?

A single, front-loaded sentence with no filler. Every word contributes to the action and target, and there is no redundant restating of the tool name.

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 zero-parameter UI opener with an output schema present, the description covers the essential invocation detail: what panel is opened. A note about prerequisites or non-destructive behavior could add context, but nothing critical is missing for a correct call.

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 tool has zero parameters, so parameter semantics are not required. The description correctly avoids inventing parameter-like options, meeting the 0-parameter baseline.

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 a specific action ('Open') and a concrete UI destination ('Rendering / Materials panel'), which clearly identifies this as a panel-opening tool rather than a material creation/assignment or rendering tool. It is specific enough to distinguish from siblings like rhino_material_create and rhino_render_setup, though it does not explicitly frame the panel's purpose.

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?

There is no guidance on when to use this tool versus alternatives, no exclusions, and no prerequisites. The intended use is loosely inferable from the verb and panel name, but an agent receives no explicit direction about when to reach for this over sibling rendering/material tools.

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