intelligent_3d_processing

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

No annotations are provided, so the description should disclose side effects and behavior. It mentions 'autonomously queries material, modeling, and IO capabilities' implying internal tool calls, but does not explain if scenes are modified in place, if results are returned, or if operations are destructive. This is a significant gap for a tool that likely alters scenes.

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 two sentences, but the first sentence is jargon-heavy ('FastMCP 3.1 SEP-1577 multi-step sampling') and the second adds context on pipeline building. It could be more concise by removing jargon and front-loading the core action. Still, it is short and not overly verbose.

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 presence of an output schema (unseen) and high schema coverage, the description should explain the tool's role as an orchestrator. It only mentions 'build a processing pipeline' without detailing what the output is, how the pipeline is structured, or what constitutes successful processing. The tool is complex (5 params, orchestration) and the description is insufficient for an agent to fully understand its behavior.

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?

Input schema covers all 5 parameters with descriptions. The description adds little beyond the schema—it references 'query material, modeling, and IO capabilities' which are not parameter names. With 100% schema coverage, the baseline is 3; the description does not provide extra semantic value to justify a higher score.

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 'Intelligent batch 3D scene processing' but is vague on the concrete action—whether it modifies, creates, or analyzes scenes. Jargon like 'FastMCP 3.1 SEP-1577 multi-step sampling' obscures the purpose. It does not distinguish from siblings like agentic_blender_workflow or export_for_mcp_handoff.

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 explicit guidance on when to use this tool vs. alternatives. The description implies it is for batch processing with multi-step reasoning, but does not state prerequisites, limitations, or when to prefer individual blender tools.

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