list_particle_systems

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

No annotations are provided, and the description discloses zero behavioral traits. It doesn't indicate whether the tool is read-only, destructive, or what side effects it might have. The agent has no insight into the tool's operational behavior.

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 under-specified rather than concise. It contains one empty sentence that adds no value. A good description should front-load useful information; this one provides none.

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 a required parameter and an output schema, but the description explains nothing about them. Given the complexity of Blender objects and the need to list particle systems, this is totally inadequate for an agent to call 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% for the parameter object_name, and the description adds no meaning to it. The agent receives no information about what object_name refers to, its format, or why it's required.

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 'Blender Studio Pro MCP: list_particle_systems' which merely restates the tool name. It does not state a specific verb, resource, or any functional detail. This is a tautology, as it repeats the title without explaining what the tool does.

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?

There is no guidance on when to use this tool versus alternatives. The description provides no context about typical use cases, prerequisites, or differentiation from sibling tools like add_particle_system or remove_particle_system.

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