particles.remove

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

With no annotations, the description only states the action without disclosing side effects, permanence, authentication needs, or error behavior. It is minimal and does not inform the agent of potential consequences.

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?

A single concise sentence with no redundancy. However, it could be slightly more structured (e.g., list parameters) without losing conciseness.

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?

For a removal operation with no output schema and no annotations, the description lacks essential context like whether removal is permanent, whether the particle system must exist, or what happens on failure. It is minimal and incomplete for safe invocation.

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?

The description repeats the parameter concepts ('named particle system', 'object') already present in the schema titles, adding no new constraints, formats, or examples. Schema coverage is 0%, and the description does not compensate.

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 the action ('Remove'), the resource ('a named particle system'), and the target ('from an object'). It is specific and distinguishes from sibling tools like particles.add, particles.report, and particles.set.

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 on when to use this tool versus alternatives such as particle deletion via other methods or when removal is appropriate. It lacks context for decision-making.

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