open_settings

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

With no annotations, the description carries the full behavioral burden. It clearly discloses that the tool opens a Settings page directly, and the page list adds useful detail. However, it does not mention prerequisites like device unlock, behavior on invalid page names, or how the optional device parameter affects which device's settings are opened.

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 short and front-loaded: the purpose appears in the first sentence, and the second sentence is a compact list of valid values. Every sentence earns its place, and the page list is necessary given the lack of an enum in the schema.

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 simple navigation tool, the description covers the core action and the main parameter's value space. It is incomplete regarding the 'device' parameter, whether the page value is case-sensitive, and what happens on invalid input. An agent could call it correctly with the required page, but the optional device semantics remain unclear.

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 does for the 'page' parameter by listing all accepted values, which is genuinely useful. However, the 'device' parameter is not explained at all, leaving its meaning and relationship to the sibling device-management tools implicit.

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 states a specific verb ('Jump straight to') and a clear resource ('a Settings page'), and enumerates the exact accepted page values. This makes the tool's purpose unambiguous and distinguishes it from general navigation or app-opening siblings.

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 phrase 'instead of navigating there by hand' gives clear context for when to use this tool: when direct access to a Settings page is needed. It doesn't explicitly name alternatives or exclusions, but the page list and sibling context make the intended usage clear.

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