Get performance settings

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safe read-only nature is covered. The description adds the specific setting categories that are read, but says nothing about return shape, defaults, or how the flags relate to reanim_set_low_end_mode; with annotations carrying the safety profile a 3 is appropriate.

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 naming the primary setting (LowEnd UI mode) first and the remaining flags after. No padding, though the trailing 'and related perf flags' is slightly vague.

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 no-parameter, no-output-schema getter with read-only annotations, the description covers what is read and is sufficient to invoke correctly. The absence of any return-shape hint is the only minor gap.

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 tool takes zero parameters, so the baseline is 4; there is nothing for the description to disambiguate beyond confirming it is a bare read.

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 (Read) plus the concrete resource (LowEnd UI mode, FXBlur, FXSounds, FXTransitions, FXAmbient and related perf flags). An agent can tell what it returns, though it does not explicitly contrast itself with near-neighbors like reanim_get_ui_theme or reanim_get_root_settings.

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 indication of when to call this versus the many overlapping getters in the sibling list (reanim_get_ui_theme, reanim_get_customization, reanim_get_root_settings, reanim_set_low_end_mode). Usage is only implied by the tool name.

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