rhino_points_on

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

The description states the primary effect (turn on control points) but with no annotations, it does not disclose side effects, limitations (e.g., unsupported object types), or behavior when nothing is selected. It is adequate but not deeply transparent.

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, short sentence fully conveys the action and target. No unnecessary words or fluff.

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 parameterless command with an output schema, the description is mostly complete: it names the target and effect. It does not mention output or error conditions, but these are likely trivial for this tool, so this is a minor gap.

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?

There are no parameters, so schema coverage is effectively complete. The description adds no parameter-specific semantics, leaving the dimension at the baseline of 3.

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?

Description uses a specific verb ('Turn on') and clearly identifies the resource ('control point display') and scope ('selected objects'). It is unambiguous and naturally distinguished from siblings like rhino_points_off.

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?

Provides clear context that the action applies to selected objects, which tells the agent when this tool is appropriate. Does not explicitly mention alternatives or exclusions, but for a simple toggle command the context is sufficient.

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