3D-MCP

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

With no annotations, the description carries full burden but provides minimal behavioral insight. It implies a write operation ('Update') but doesn't disclose critical traits like permission requirements, whether updates are destructive or reversible, error handling for invalid IDs, or if it's atomic (all-or-nothing). The description adds no context beyond the basic action, leaving significant gaps 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 a single, efficient sentence with no wasted words, making it appropriately concise. However, it's front-loaded only in the sense that it's brief, but it lacks structural elements like clarifying the domain or usage, which could improve clarity without sacrificing brevity.

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 tool's complexity (batch update of Constraints with many nested parameters), no annotations, and no output schema, the description is incomplete. It fails to explain what Constraints are, the impact of updates, return values, or error conditions. For a mutation tool in a 3D modeling context, this leaves the agent with insufficient information to use it 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 'items' parameter and its nested properties. The description adds no meaning beyond what the schema provides—it doesn't explain the structure of 'items', clarify that 'ids' are required, or give examples. With high schema coverage, the baseline is 3, and the description doesn't compensate with additional insights.

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 states the action ('Update') and resource ('multiple Constraints'), which provides a basic purpose. However, it's vague about what Constraints are (3D modeling constraints like point, aim, etc.) and doesn't differentiate from sibling tools like 'updateBlendShapes' or 'updateMaterials' beyond the resource name. It lacks specificity about the operation's scope or domain context.

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. It doesn't mention prerequisites (e.g., existing Constraints), compare to single-update tools if they exist, or specify scenarios like batch operations. The description only restates the tool's function without contextual usage advice.

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