Set low end mode

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

Annotations only declare readOnlyHint=false and openWorldHint=false (a non-read mutation, non-open-world), so the description carries real weight. It usefully discloses the effects of each state — 'basic UI + simplified triangle' for ON and 'restores your settings' for OFF, implying previous settings are retained — which is added value beyond the annotation.

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 tight sentence with an em-dash separating the location hint from the state semantics; nothing is wasted and the core action is front-loaded. Minor cost from the 'Toggle' vs 'set' wording mismatch.

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 single-boolean, no-output-schema tool with full schema coverage, the description supplies enough to call it correctly, including both state effects. Only the when-to-use routing is missing.

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 100% and the schema already states true=ON / false=OFF, so baseline would be 3. The description goes further by explaining what each state actually does to the UI and settings, giving the agent semantic grounding for the boolean beyond a bare label.

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?

States a specific verb+resource (set/toggle LowEnd UI Mode) and even locates it in the UI (Main page > Performance). However, the description says 'Toggle' while the tool name is 'set_low_end_mode' and it requires an explicit boolean, so the framing is slightly inconsistent and doesn't differentiate it from siblings like reanim_set_root_mode or reanim_set_ui_theme.

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 when-to-use or when-not-to-use guidance, and no alternatives named among the many sibling setters. The UI path ('Main page > Performance') gives incidental context but doesn't help an agent decide when this tool is the right pick.

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