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. It only states 'Create multiple Materials' without explaining what happens upon creation (e.g., are materials added to a scene, saved to a file, require specific permissions, have side effects like resource allocation, or return identifiers). This is inadequate for a mutation tool with zero annotation coverage.

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 two words, front-loading the key action and resource. There is no wasted language, making it efficient for quick scanning, though this conciseness comes at the cost of detail.

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 the complexity of creating materials with multiple nested properties (as shown in the schema), no annotations, and no output schema, the description is incomplete. It doesn't explain the purpose, usage context, behavioral aspects, or what to expect after creation, leaving significant gaps for an AI agent to understand and use the tool effectively.

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 meaning beyond implying multiple items can be created, which is already clear from the schema. Baseline 3 is appropriate when the schema does all the work.

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 Materials' states the action and resource but is vague about what 'Materials' are in this context (3D modeling materials, educational materials, etc.). It distinguishes from siblings like 'createMeshs' or 'createUVMaps' by specifying 'Materials', but lacks specificity about the domain or what creation entails beyond the basic verb.

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. Sibling tools include 'createMeshs', 'createUVMaps', and 'updateMaterials', but the description doesn't indicate when creation is appropriate over updates or how it relates to other creation tools. There's no mention of prerequisites, context, or exclusions.

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