switch_curve_direction

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

No annotations are given, so the description must fully disclose behavior. It states it 'switches direction' but does not explain what this entails (e.g., reversing normals, tangency changes, or if it's destructive). The effect on the curve is ambiguous, and no prerequisites or side effects are mentioned.

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 concise, consisting of a one-sentence purpose followed by a structured Args/Returns section. Every part is necessary, though the Returns section is terse. No redundancy or superfluous text.

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's simplicity (one parameter, no output schema provided), the description covers the essential purpose and parameter. It does not explain the return value (confirming direction switch) beyond a dict, but with an output schema present, this is acceptable. Could mention any prerequisites like the curve type or if it works on all curves.

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 only parameter, curve_name, is described as 'Name of the curve object,' which matches the name. With 0% schema description coverage, the description adds minimal value beyond the parameter name. However, the tool has only one parameter, so the description is adequate but not insightful.

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 'Switch the direction of a curve's splines' uses a specific verb and resource, clearly indicating the tool's function. It distinguishes itself from sibling curve tools like 'set_curve_property' or 'convert_curve_to_mesh' by focusing on direction reversal.

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 lacks any guidance on when to use this tool versus alternatives, such as when to reverse spline direction vs. using 'set_curve_property' for other attributes. No when-to-use or when-not-to-use details are provided.

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