generate_bezier_path

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

No annotations provided, and the description fails to disclose whether the tool has side effects, is read-only, or requires specific authorization. It doesn't mention error conditions or performance characteristics.

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?

Description is short and structured with parameter and return sections. No redundant information, but could be more formal.

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?

Tool likely outputs a path list for robot movement, but the return format is not detailed (are points 3D positions only?). No output schema. Missing context on how output relates to sibling tools like movel.

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 adds structure for control_points (format as list of objects with x, y, z, rx, ry, rz) and explains num_points. However, it doesn't explain constraints on control_points (e.g., minimum number) or the default behavior fully.

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?

Description clearly states it generates a Bezier curve path using control points. Verb and resource are specific. However, it doesn't distinguish itself from sibling tools like optimize_trajectory or draw_circle, which might have overlapping functionality.

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 vs alternatives (e.g., movej, movel, draw_circle). It doesn't mention prerequisites, limitations, or context for usage.

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