convert_object

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

No annotations provided, so description must disclose behavioral traits. It states returns a confirmation dict but does not clarify whether the conversion alters the object in place or creates a new one, nor side effects (e.g., on materials or modifiers). Risk of unexpected behavior.

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 uses a structured docstring with Args and Returns sections, clearly separating parameter description from return info. It is slightly verbose for a simple conversion, but all information is relevant and easy to parse.

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 complexity of object conversion (handling materials, data, scene hierarchy), the description is minimal. It mentions return type but not failure conditions or object selection method. With an output schema present, the return info is adequate, but behavioral details are missing.

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 has 0% description coverage, so description compensates by listing valid target types (MESH, CURVE, etc.) beyond the schema's default. However, the object_name parameter lacks additional context (e.g., how to reference an existing object). The target list is explicit and helpful.

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 'Convert an object to a different type.' It specifies the action (convert), the resource (object), and the outcome (type change). The target parameter lists exact values (MESH, CURVE, etc.), making the tool's function distinct from siblings like 'convert_curve_to_mesh' which handle specific conversions.

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?

Description implies usage for general type conversion but provides no explicit guidance on when to prefer this over specific tools like 'convert_curve_to_mesh' or limitations (e.g., which object types are convertible). Lacks context on prerequisites or alternatives.

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