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

Annotations already declare readOnlyHint, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds genuine non-obvious context: data is device-local, includes defaults and recent history, and no shared plan is mutated — exactly the kind of scoping detail annotations cannot express.

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?

Two short sentences with zero filler, and the core action ('Open local widget preferences') is front-loaded ahead of the scoping caveat. Every clause earns its place.

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 zero-parameter, no-output-schema tool the description is nearly complete: it says what opens and that nothing shared is affected. It does not describe what the agent should expect to see afterward, but with annotations covering the read-only profile this is a 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 and the schema coverage is 100%, so there is nothing for the description to disambiguate. Baseline 4 applies; no parameter information is missing or contradictory.

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 ('Open local widget preferences') and the description clarifies scope ('on this device'), which separates it from the shared-plan siblings. It does not explicitly distinguish itself from read_plugin_settings/update_plugin_settings, and the mismatch between the title ('Device preferences') and the description ('widget preferences') leaves minor ambiguity about what is actually opened.

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 sentence 'does not change a shared plan' gives an implicit when-not boundary, useful against the plan-mutation siblings. However, no alternative is named and no condition for choosing this tool over read_plugin_settings is stated, so the guidance is only implied.

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