mesh.edit

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

Annotations already establish this is a mutating, non-idempotent operation, so the description should add context beyond that, but it only offers 'Risk: standard; maturity: L3'. It fails to disclose that some operations (delete, weld, recalculate_normals) permanently alter or remove geometry, or that the tool is coupled to a transaction id and expected scene revision protocol. No contradiction with annotations exists, but the disclosure is thin for a state-changing tool.

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 text is short, but brevity reflects omission rather than efficiency. The opening sentence is a near-tautological restatement of the tool name and title, and the second is a generic policy disclaimer; neither earns its place by informing the agent.

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?

This is a high-complexity tool with 13 parameters, a 9-operation enum, a nested selection receipt, and transaction/authorization fields, yet the description explains none of it. The operation-to-parameter pairing, the role of the selection receipt from mesh.select, and the transaction protocol are all left to the agent to infer from the schema.

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 only 38%, leaving 8 of 13 parameters undocumented, and the description adds zero parameter information. An agent gets no help pairing parameters to operations (cuts/segments for bevel/subdivide, thickness for extrude/inset, distance for bridge/weld) and no units or constraints beyond what the schema sporadically provides.

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 reads 'PartMe Blender Harness command `mesh.edit`', which merely restates the tool name/title and never states what the tool does. The actual purpose (modifying mesh geometry via extrude, bevel, subdivide, delete, etc.) is only inferable from the schema's operation enum, not from the description text.

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 about when to use this tool versus alternatives such as blender_mesh_select, blender_mesh_inspect, or blender_object_delete. The only behavioral note, 'Per-request argument checks and session policy still apply', is an operational policy reminder rather than usage direction.

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