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 Curves', implying a destructive mutation, but lacks details on permissions, reversibility (e.g., via 'undo'), side effects, or error handling. For a deletion tool with zero annotation coverage, this is a significant gap in 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 a single, efficient sentence with zero waste: 'Delete multiple Curves'. It is front-loaded and appropriately sized for the tool's purpose, making it easy to parse quickly.

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 (destructive deletion with no annotations and no output schema), the description is incomplete. It lacks information on behavioral traits, return values, or error conditions. For a mutation tool, this leaves significant gaps for an AI agent to understand proper invocation and outcomes.

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' documented as 'Curve identifiers to delete'. The description adds no additional parameter semantics beyond what the schema provides, such as format examples or constraints. With high schema coverage, the baseline score of 3 is appropriate as the description doesn't compensate but doesn't need to.

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 Curves' clearly states the action (delete) and resource (Curves), with 'multiple' indicating batch capability. It distinguishes from sibling tools like 'deleteEdges' or 'deleteFaces' by specifying the resource type. However, it doesn't explicitly differentiate from 'deleteCurves' (singular) if such a tool existed, though siblings show only this plural version.

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., whether curves must exist or be selected), exclusions, or comparisons to similar tools like 'delete' (general) or 'clearSelection'. The description is purely functional without contextual advice.

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