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. 'Delete' implies a destructive mutation, but it doesn't disclose whether deletion is permanent, reversible (e.g., via undo), requires specific permissions, or has side effects on related data. For a destructive tool with zero annotation coverage, this is inadequate behavioral disclosure.

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 at three words, front-loaded with the core action. There's zero waste or redundancy, 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 tool's destructive nature, lack of annotations, and no output schema, the description is incomplete. It doesn't explain what keyframes are, the impact of deletion, error conditions, or return values. For a mutation tool with significant behavioral implications, more context is needed.

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 the parameter 'ids' clearly documented as 'Keyframe identifiers to delete'. The description adds no additional meaning beyond what the schema provides, but the baseline is 3 when schema coverage is high (>80%) and no param info is in the description.

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 Keyframes' clearly states the verb (delete) and resource (keyframes), but it's vague about scope and doesn't differentiate from sibling tools like deleteKeyframes vs deleteChannels or deleteClips. It doesn't specify what keyframes are in this context or what happens when they're deleted.

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 on when to use this tool versus alternatives. There's no mention of prerequisites (e.g., needing existing keyframes), consequences of deletion, or comparison to related tools like deleteKeyframes vs updateKeyframes or createKeyframes. The description provides only basic functionality without context.

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