3D-MCP

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

With no annotations provided, the description carries full burden for behavioral disclosure. 'Set' implies a mutation operation, but the description doesn't mention whether this requires specific permissions, whether changes are destructive or reversible, what happens to existing subdivision levels, or what the typical response looks like. 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 - a single sentence with zero wasted words. It's front-loaded with the essential information and doesn't contain any unnecessary elaboration or repetition.

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 insufficiently complete. It doesn't address behavioral aspects like side effects, permissions needed, error conditions, or what constitutes success. Given the complexity implied by setting subdivision levels on surfaces, more context about what this operation actually does would be valuable.

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. The description doesn't add any meaningful parameter semantics beyond what's in the schema - it doesn't explain what 'subdivision levels' mean in practice, valid ranges beyond the minimum, or typical use cases for setting multiple levels at once.

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 clearly states the action ('Set') and target resource ('subdivision levels for surfaces'), making the purpose immediately understandable. However, it doesn't distinguish this tool from similar sibling tools like 'updateSubdivisionSurfaces' or 'getSubdivisionSurfaces', which would require more specific differentiation.

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 no guidance on when to use this tool versus alternatives. With sibling tools like 'updateSubdivisionSurfaces' and 'getSubdivisionSurfaces' available, there's no indication of whether this is for bulk operations, specific use cases, or how it differs from the 'update' variant.

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