3D-MCP

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

No annotations are provided, so the description carries full burden. It states 'Delete multiple Drivers' which implies a destructive mutation, but doesn't disclose critical behavioral traits: whether deletion is permanent/reversible, what permissions are required, if there are side effects (e.g., breaking dependencies), or rate limits. For a destructive tool with zero annotation coverage, this is inadequate.

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, front-loading the essential action and resource. There's zero wasted language, making it efficient for quick comprehension, though this conciseness comes at the cost of completeness.

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 this is a destructive mutation tool with no annotations and no output schema, the description is incomplete. It doesn't explain what Drivers are, the consequences of deletion, error conditions, or return values. For a tool that permanently removes resources, more context is needed to use it safely and 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% with one parameter 'ids' described as 'Driver identifiers to delete'. The description adds no additional parameter information beyond what the schema provides. With high schema coverage and only one parameter, the baseline is high, but the description doesn't compensate with format examples or constraints.

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 'Delete multiple Drivers' clearly states the action (delete) and resource (Drivers), but it's vague about what 'Drivers' are in this context. It distinguishes from sibling tools like 'deleteBlendShapes' or 'deleteMaterials' by specifying the resource type, but doesn't explain what Drivers represent in this system.

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 about when to use this tool versus alternatives. The description doesn't mention prerequisites (e.g., needing existing Drivers), what happens after deletion, or when to use batch deletion versus individual deletion. Sibling tools include 'getDrivers' and 'listDrivers' which might be used first, but this isn't stated.

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