curve.to_mesh

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

Annotations are all false, providing no safety profile, and the description adds no behavioral context. It mentions 'Risk: standard' and 'maturity: L3' but these are metadata, not behavior. There is no disclosure of side effects, mutation, or scene changes. For a likely mutating operation (curve to mesh), this is a critical gap.

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 extremely short (one sentence), which could be seen as concise, but it is under-specified rather than efficiently informative. There is no wasted text, but the content fails to convey essential purpose or usage. It is more of a placeholder than a concise summary.

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 tool with 6 parameters, an output schema, and a likely complex operation (converting curves to meshes), the description is completely inadequate. It provides no context on inputs, expected output, or behavior, and does not compensate for the missing schema descriptions on key parameters.

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 provides no explanation of any parameters. The schema has descriptions only for harness plumbing parameters (_requestId, _authorization, _transactionId), while the tool-specific parameters (name, objectId, _expectedSceneRevision) have no descriptions. The description adds no meaning to any parameter.

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 is essentially a tautology: it states 'PartMe Blender Harness command `curve.to_mesh`' without explaining what the command does. It does not use a verb+resource format, and it fails to distinguish the tool from siblings like blender_curve_create or blender_mesh_edit. An agent cannot infer the operation from the description alone.

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?

There is no guidance on when to use this tool versus alternatives, no context for selection, and no exclusions or prerequisites mentioned beyond generic 'session policy' which applies to all tools. The description does not reference sibling tools or conditions for use.

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