rhino_loft

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

Annotations already indicate readOnlyHint=false, so the description's mention of creating a surface is consistent. However, it adds no extra behavioral context such as whether the operation is destructive, requires specific curve types, or how errors are handled. The description is minimal and redundant with the title.

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, which is concise, but it lacks structure and depth. It is not a tautology but is too brief to be informative. Every word earns its place, but more substance is needed.

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?

Given the tool has multiple parameters, no schema descriptions, and an output schema (not shown), the description is severely lacking. It does not cover the loft operation's nuances, parameter roles, or output nature. The context is 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?

The description does not explain any of the input parameters (profile_ids, closed, loft_type, etc.). Schema description coverage is 0%, so the description should compensate but fails to do so. The agent cannot infer parameter semantics from this description alone.

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 the verb 'loft' and resource 'profile curves' with output 'surface', clearly indicating the operation. However, it does not explicitly differentiate this tool from sibling surface creation tools like sweep1, sweep2, or network surface, which are similar in purpose.

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. It lacks explicit when-not conditions, prerequisites, or comparisons to sibling tools. The user is left to infer usage from the name alone.

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