rhino_show_endpoints

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does not state whether this affects selected curves, all curves, or the current document view, nor does it mention side effects, persistence, or prerequisites. The description mostly restates the parameter behavior rather than revealing additional behavioral context.

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 short, front-loaded with the primary action, and includes a concise parameter explanation. Every sentence contributes useful information with no filler or redundancy.

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 single-boolean tool, the description is adequate, but it omits important context such as whether the operation applies to selected objects or the whole document. The existence of an output schema reduces the need to document return values, but the missing scope/selection context leaves the definition only minimally complete.

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 0%, so the description must compensate. It does add meaning by explaining that show=True displays endpoints and show=False hides them. This directly clarifies the boolean parameter's semantics beyond the raw schema field.

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 a specific action and resource: 'Toggle display of curve endpoints.' This distinguishes it from sibling tools like rhino_show_edges and rhino_show_dir by focusing specifically on curve endpoints. The term 'Toggle' is slightly imprecise since the parameter actually sets a state, but the Args text clarifies the intended behavior.

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 description provides no guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. It is only implied that one should use it when wanting to control curve endpoint visibility, but there is no explicit context or comparison with sibling tools.

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