merge_by_distance

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does not describe what the tool does (e.g., merges vertices within a threshold distance), effects on selection, or side effects. There is no behavioral information beyond the name.

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 short, but it is under-specified rather than concise. Each word is wasted, as it only repeats the tool name. There is no front-loaded useful 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 mesh operation that affects geometry, the description is completely inadequate. It provides no information about behavior, parameter semantics, output, or prerequisites. The output schema exists but cannot compensate for the missing description.

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 has a single 'threshold' parameter with no description, and schema description coverage is 0%. The description does not explain the meaning of 'threshold' (e.g., distance in Blender units, default 0.0001). With zero coverage, the description must compensate but does not.

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 'Blender Studio Pro MCP: merge_by_distance', which merely restates the tool name. It does not state a specific verb or resource beyond the name itself, nor does it differentiate from sibling tools like delete_geometry or apply_bmesh_op. This is a tautology.

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. There is no mention of the intended context (e.g., mesh editing, vertex merging) or exclusions. The description offers zero usage direction.

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