Extract a Bezier sub-curve for a specified parameter range using de Casteljau subdivision to isolate curve segments.
Extract a Bezier sub-curve for a parameter range using de Casteljau subdivision.
| Name | Required | Description | Default |
|---|---|---|---|
| t_end | Yes | End parameter (0-1) | |
| t_start | Yes | Start parameter (0-1) | |
| control_points | Yes | Array of [x,y] control points |
Changes observed during successful MCP inspections.
v0.1.11Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. It mentions the subdivision algorithm but does not disclose whether the operation is pure, whether it mutates the input control points, what the output format is, or any edge-case behavior. This leaves significant behavioral gaps for an agent.
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, front-loaded sentence with no redundant information. Every word contributes to the purpose.
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?
For a deterministic geometry tool with 100% schema coverage, the description is minimally adequate. However, with no output schema and no annotations, it does not explain the return value (e.g., a new list of control points) or any operational constraints, leaving the agent to infer these.
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 100%, so the schema fully documents the three parameters. The description adds no parameter-specific details beyond what is already in the schema, which meets the baseline of 3 for high coverage.
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 a specific verb ('Extract') and resource ('Bezier sub-curve') and specifies the algorithm ('de Casteljau subdivision'). It distinguishes itself from sibling 'bezier_curve' by focusing on a sub-curve rather than the whole curve, but does not explicitly name the sibling or contrast behaviors.
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 when-to-use guidance or alternatives are provided. The description only states what the tool does, not when to choose it over other Bezier-related tools like bezier_curve.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.