Result set particles

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

Annotations already declare readOnlyHint=false, idempotentHint=true and destructiveHint=false, so the agent knows this mutates viewer state safely and repeatably. The description adds that the mutation targets particle rendering specifically, but says nothing about whether the setting applies immediately, persists across sessions, or is scoped to the current result set.

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 front-loaded sentence with no filler. It is efficient, though its brevity is as much under-specification as conciseness given the undocumented parameters.

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 rendering-configuration tool with three undocumented parameters and no output schema, the description is too thin. It does not say whether settings apply to the active dataset, whether all parameters are optional and default to the current values, or what visual effect each render mode produces.

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?

All three parameters (visible, pointSize, renderMode) have 0% schema description coverage, and the description names none of them. With the enum values (points/sprite/sphere) and pointSize having no units or valid range, the description was the only place to compensate and it does not.

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?

Specific verb (Configure) plus resource (particle rendering in the result viewer) tells the agent exactly which subsystem is affected. It does not differentiate itself from close siblings like result_set_colormap or result_set_active_dataset, but the purpose itself is unambiguous.

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 when-to-use guidance, no prerequisites, and no mention of the other result_* viewer tools. The agent must infer from the name alone that this is the tool for toggling/sizing particles rather than, say, colormaps or probes.

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