convert_to_mesh

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

The annotation destructiveHint=true already discloses mutability, but the description adds specific behavioral context: it explicitly warns that curve editability is lost. This goes beyond the generic annotation, explaining what is destroyed. However, it does not mention other potentially relevant side effects (e.g., whether the curve object is replaced or a new object is created).

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 two sentences, front-loaded with the core purpose followed by a single caveat. Every word earns its place; there is no padding or redundancy.

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 single-parameter conversion tool with an output schema, the description is adequate but not complete. It lacks guidance on how to identify the object, what happens to the original curve, and how errors (e.g., non-curve input) are handled. The output schema may cover return values, but parameter semantics remain a significant gap.

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 schema exposes one required string parameter 'object' with zero description coverage. The description does not explain what value should be passed (e.g., object name, ID), nor does it mention validation requirements. 'Convert a curve object' only implies the target is a curve, but the parameter format is left entirely to inference.

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 clearly states the specific action ('Convert a curve object') and result ('to a mesh'). It differentiates from siblings like get_curve_info or create_curve by naming the transformation. The added caveat 'Loses curve editability' further defines the 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?

No guidance is provided on when to use this tool versus alternatives. It does not mention prerequisites (e.g., the object must be a curve), when not to use it, or relationships to sibling tools like apply_modifier or remesh. The description only states what the tool does, not when to select it.

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