3D-MCP

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

No annotations are provided, so the description carries the full burden. 'Create multiple Vertexs' implies a write operation but doesn't disclose behavioral traits like whether this requires specific permissions, if it's idempotent, what happens on failure, or how it interacts with existing geometry. The description is minimal and lacks crucial context for a mutation 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 description is extremely concise with just three words. It's front-loaded and wastes no words, though this conciseness comes at the cost of completeness. Every word directly relates to the tool's purpose.

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 mutation tool with no annotations and no output schema, the description is inadequate. It doesn't explain what a 'Vertex' is, how creation affects the system, what the return value might be, or error conditions. The high schema coverage helps with parameters, but overall context is severely lacking.

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 100%, so the schema fully documents the single parameter 'items' and its nested properties. The description adds no additional parameter semantics beyond what the schema provides, which meets the baseline for high schema coverage.

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 'Create multiple Vertexs' restates the tool name with minor variation, making it tautological. It specifies the verb 'Create' and resource 'Vertexs' but lacks specificity about what a 'Vertex' is in this context or how this differs from similar tools like 'createMeshs' or 'createEdges'.

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 are many sibling creation tools (e.g., createMeshs, createEdges, createFaces), but the description offers no context about when vertex creation is appropriate, prerequisites, or exclusions.

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