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 read-only or mutation operation (though 'perform operations' suggests mutation), what permissions might be required, whether operations are atomic or batched, what happens on failure, or what the tool returns. For a tool that appears to modify group memberships, this lack of behavioral information is a significant gap.

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?

While technically concise with just three words, this is a case of under-specification rather than effective conciseness. The description doesn't earn its place by adding value beyond what's already obvious from the tool name. It's front-loaded only because it's so brief, but the brevity comes at the cost of being unhelpful for tool selection and invocation.

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 group operations in a 3D modeling context with no annotations and no output schema, the description is completely inadequate. It doesn't explain what 'object groups' are, what operations can be performed (though the schema shows add/remove/move/nest), what the tool returns, or how it differs from related sibling tools. For a mutation tool with batch operations capability, this minimal description leaves critical gaps.

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%, with both parameters ('operation' and 'items') well-documented in the schema itself. The description adds no additional parameter information beyond what's already in the structured schema. According to the scoring rules, when schema_description_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 'Perform operations on object groups' is a tautology that essentially restates the tool name 'performGroupOperations'. It lacks specificity about what types of operations are performed (add, remove, move, nest) or what 'object groups' refer to in this 3D modeling context. While it mentions the general domain, it doesn't provide the verb+resource clarity needed to distinguish it from sibling tools like 'createGroups', 'deleteGroups', or 'updateGroups'.

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 about when to use this tool versus alternatives. It doesn't mention prerequisites, appropriate contexts, or relationships to sibling tools like 'createGroups' or 'updateGroups'. With 75+ sibling tools in this 3D modeling environment, the lack of any usage guidance makes it difficult for an AI agent to determine when this specific group operation tool is appropriate.

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