get_rendering_settings

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description adds real value beyond that: it clarifies that rendering_api is the RHI in use, that many flags are read from console variables, and that 'world_*_enabled' indicates physical world contents (a light, a shadow caster, a height fog, a sky atmosphere) rather than settings toggles. It does not say what happens when settings cannot be read, which the 'rendering_settings_found' field implies.

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?

The first sentence is well front-loaded and the Returns block earns its place given there is no output schema. However, it is delivered as one enormous comma-separated run-on with heavy 'rendering_' and 'world_' prefix repetition, and fields like 'rendering_vsync_enabled?' and 'rendering_resolution_x?' carry unexplained question marks. The information is present but poorly structured.

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?

With no output schema, the description correctly carries the full burden of describing return values and does enumerate the complete field inventory plus clarifications for the ambiguous groups. Two gaps remain: the meaning of the '?' suffixes on several fields is never explained, and there is no note on what the found/message pair indicates when settings are unavailable.

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 per the baseline rule this is a 4. There are no parameter semantics to add, and the description correctly spends its space on the return payload instead of inventing parameter detail.

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 and resource ('Retrieve current rendering settings') and enumerates the categories covered: quality levels, rendering mode, world settings, engine version, feature states. It is clearly a read-only introspection tool, but it never distinguishes itself from adjacent readers such as get_engine_settings, get_lighting_quality, or get_post_process_settings, all of which overlap in scope.

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?

The description contains no when-to-use guidance, no prerequisites, and no named alternatives. An agent must infer from the name alone that this is for inspecting current render configuration rather than for changing it, and cannot tell whether to prefer this over get_engine_settings or get_lighting_quality for overlapping data.

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