quest_set_refresh_rate

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

With no annotations, the description bears the burden of disclosing behavior. It correctly notes that this is a 'hint' and that apps can override it, which is a crucial nuance. It doesn't cover persistence or connection requirements, but it covers the most important behavioral caveat.

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 description is two sentences, front-loaded with the verb, and contains no unnecessary information. It is concise and well 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?

Given the simple tool and minimal schema, the description covers essential purpose, valid values, and a critical caveat. It omits details about device_id and potential return/error behavior, but overall it provides sufficient context for basic usage.

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 description coverage is 0%, so the description must compensate. It explains the 'rate' parameter by listing allowed values, but it doesn't clarify the 'device_id' parameter or its default behavior. This partial clarification earns a middle score.

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 tool sets a display refresh rate hint, specifying the resource (display) and action (set). It also includes specific allowed values, distinguishing it from other Quest-related tools that don't address refresh rate.

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?

It provides context by identifying the target device (Quest 3) and valid rates, and warns that apps requesting an explicit rate override the hint. It doesn't explicitly name alternatives or exclusions, but the use case is clear enough.

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