rhino_points_solid_on

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

No annotations are present, so the description must fully disclose behavior. It only says 'Enable solid point display,' which conveys a basic non-destructive display action but does not mention selection requirements, persistence, toggling semantics, or any side effects. This leaves important behavioral context undisclosed.

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 with no filler. It states the action and the applicable object type efficiently, which is appropriate for a zero-parameter tool.

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 no-parameter display toggle, the description covers the core operation and an output schema exists to handle return values. However, the presence of near-duplicate siblings and the lack of any note about object selection or when this differs from rhino_points_on leave some contextual ambiguity.

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 input schema has zero parameters and schema description coverage is 100%, so the description does not need to explain any parameters. The tool's focus on enabling a display mode is sufficient given there is nothing to configure.

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 and resource: enabling solid point display for solid/closed objects. It is clear about what the tool does, but it does not differentiate itself from the similarly named sibling 'rhino_solid_pt_on', which appears to represent nearly the same operation.

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 phrase 'for solid/closed objects' implies when the tool should be used, distinguishing it from generic point display tools like rhino_points_on. However, no explicit guidance or exclusions are provided regarding alternatives such as rhino_solid_pt_on or rhino_points_solid_on's relationship to other display toggles.

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