3D-MCP

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 but provides none. It doesn't indicate whether this is a destructive operation, whether it requires specific permissions or context, what happens to existing vertex data, or what the expected outcome looks like. For a tool that modifies geometry vertices, this lack of behavioral information is particularly problematic.

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 maximally concise - just three words. While this represents under-specification rather than ideal conciseness, according to the scoring framework, 'Process' received a 2 for being under-specified, but this description is even more minimal. However, every word earns its place, and there's zero redundancy or wasted text.

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 that this is a mutation tool (transforming vertices implies modification) with no annotations, no output schema, and complex nested parameter structure, the description is completely inadequate. It doesn't explain what 'transform' means operationally, what the tool returns, or provide any context about the transformation behavior. For a geometry manipulation tool, this level of incompleteness is severe.

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 description coverage is 100%, so the schema already documents the single 'items' parameter and its nested structure thoroughly. The description adds no parameter information beyond what's in the schema. According to scoring rules, when schema coverage is high (>80%), the baseline is 3 even with no param info in the description, which applies here.

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 'Transform multiple vertices' is a tautology that essentially restates the tool name 'transformVertices'. It doesn't specify what kind of transformation occurs (position, normal, offset) or what resource is being transformed. While the name suggests 3D geometry operations, the description adds no meaningful clarification beyond the name itself.

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?

The description provides absolutely no guidance on when to use this tool versus alternatives. With sibling tools like 'batchTransform', 'transformUVs', 'updateVertexs', and various vertex manipulation tools in the list, there's no indication of when this specific vertex transformation tool is appropriate versus other transformation or update operations.

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