rhino_flow

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

Annotations already indicate readOnlyHint=false, so the mutation is clear. The description adds no additional behavioral context—e.g., whether objects are copied or moved, what 'bridge only' entails, or any side effects like layer changes. It fails to add value beyond the annotation.

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 sentence with no waste. However, it is too brief and could be expanded to include essential context without becoming verbose. It is appropriately front-loaded but lacks substance.

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?

Despite having an output schema (unknown content) and annotations, the description fails to provide a complete picture. It does not explain 'bridge only,' the relationship to the sibling, or the outcome of the flow operation. Given the complexity of the input schema (4 parameters), the description is inadequate.

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 explain parameter meanings. It mentions 'one curve' and 'another,' which correspond to base_curve_id and target_curve_id, but it does not clarify object_ids or doc_id. No parameter details are provided, leaving the agent to guess.

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 'Flow objects from one curve onto another (bridge only).' This clearly identifies the action (flow) and resources (objects, curves), and hints at a specific variant ('bridge only'). However, it does not distinguish from the sibling tool 'rhino_flow_along_curve', which likely performs a similar 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?

No guidance on when to use this tool versus alternatives. There is no mention of prerequisites, limitations, or when not to use it. The description lacks any context for the agent to decide between this and the similar 'rhino_flow_along_curve'.

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