remove_particle_system

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

There are no annotations to rely on, and the description provides no behavioral disclosure. It does not mention side effects, prerequisites, or what happens when removing a particle system. The description is silent on any operational traits.

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 short, but this is under-specification rather than conciseness. No meaningful content is provided, so the brevity fails to serve the agent. A 2 reflects that while the length is minimal, it lacks any informative structure.

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?

The tool has an output schema but the description provides no context about return values or any aspect of the operation. For a tool with two parameters and no annotations, this description is entirely inadequate for an agent to call it correctly.

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 0%, and the description does not explain any parameters. Both 'object_name' and 'system_name' are entirely undocumented in both the schema and description, leaving the agent without guidance on what values to supply.

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 is a tautology: 'Blender Studio Pro MCP: remove_particle_system' simply restates the tool name with a prefix. It provides no verb, resource, or scope details that would help an agent understand what the tool does beyond its name.

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 given on when to use this tool or how it differs from siblings like 'add_particle_system' or 'list_particle_systems'. The description offers zero contextual information about appropriate usage scenarios.

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