convert_to_mesh

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

The description adds a specific behavioral consequence beyond the destructiveHint annotation: 'Loses curve editability' explicitly states what is destroyed. This is valuable context, and it aligns with the annotation (no contradiction).

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 short sentences, front-loaded with the action and result. Every word earns its place; no redundant information.

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 simple one-parameter tool with an output schema and destructiveHint annotation, the description is adequate. It covers the core behavior and a key consequence, though it could hint at object identification format or failure conditions for non-curve objects.

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 coverage is 0%, and the description does not explain the 'object' parameter beyond implying it is the curve object. It lacks details about how to specify the object (name, path, etc.), leaving a significant gap for a parameter with no schema description.

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 action: 'Convert a curve object to a mesh.' It names both the input type (curve) and output (mesh), distinguishing it from sibling tools like create_curve or get_mesh_info. The consequence 'Loses curve editability' adds specificity.

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?

It implies usage when a mesh representation is needed from a curve, and the warning about losing editability indicates a caution against converting if curve editing is still required. However, no explicit alternatives or when-not-to-use guidance are provided, so it's not a 5.

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