rhino_flow_along_curve

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

Annotations lack readOnlyHint or destructiveHint. Description does not mention default behavior (e.g., make_copy default true), side effects, or what happens to input objects. Minimal behavioral disclosure.

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?

Single sentence of 11 words is concise and front-loaded. However, it may be too minimal; a bit more detail could be added without harming 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?

Description is insufficient given the tool has an output schema and 4 parameters (nested). Lacks details on return values, behavior of 'reposition', and prerequisites. Incomplete for effective use.

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%. Description does not explain parameter meanings beyond the schema's minimal descriptions of base_curve_id and target_curve_id. No added value for parameters.

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 'Reposition objects from a base curve onto a target curve' clearly states the action (reposition) and the resources (objects, base curve, target curve). It distinguishes the tool from siblings like rhino_move or rhino_orient by specifying the transformation along curves.

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 such as rhino_flow or rhino_orient. No prerequisites, implicit usage, or exclusion criteria provided.

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