particle_set_properties

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

Description lacks behavioral details beyond the action. No annotations exist, so the description should disclose side effects (e.g., whether emission restarts, if changes are immediate), but it only says 'Returns: Success message or error description.' This is minimal.

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?

Reasonably concise given the number of parameters. Uses a clear Args section with a category header. No superfluous sentences, but some parameter descriptions could be more compact.

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?

Covers input parameters well but lacks detailed output description ('Success message or error description' is vague). No behavioral context. Given the tool complexity and lack of annotations, additional context (e.g., that this modifies an existing system) would improve completeness.

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 coverage is 0%, so parameter descriptions are critical. Each parameter has a brief, clear description (e.g., 'lifetime: Particle lifetime in seconds'). The direction and gravity parameters mention JSON array format, which adds value beyond the schema's type definitions.

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 clearly states 'Set properties of a particle system,' using a specific verb and resource. It distinguishes from sibling tools like 'particle_add_system' (add) and 'particle_start_emitting' (start), which have different actions.

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 versus alternatives. The description does not mention prerequisites, order of operations, or scenarios where another tool would be more appropriate.

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