devicelens_open_device_properties

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

The description claims the tool never changes any setting, yet the annotation readOnlyHint is false, indicating the operation may modify state. This contradiction reduces transparency. The description does add context beyond annotations (listing never-performed actions), but the contradiction is severe.

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 concise and well-structured, with a clear first sentence stating the core purpose, followed by essential usage details and behavioral caveats. No redundant words.

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 tool's simple functionality (opening a dialog) and the existence of an output schema, the description covers all necessary context: what it does, input requirements, limitations, and behavioral boundaries. It is complete without being verbose.

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?

With 0% schema description coverage, the description fully compensates by explaining the 'interface' parameter format, providing examples ('D03.2'), and specifying its source (devicelens_explain_device). This adds clear, actionable meaning.

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 opens the Windows Properties dialog for a specific device interface without modifying anything. It uses specific verbs ('open', 'without changing') and differentiates from sibling tools like devicelens_explain_device by explicitly listing actions it does not perform.

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 explicit guidance on input format (e.g., 'D03.2' from devicelens_explain_device or a full device instance ID) and clarifies that opening the dialog does not permit subsequent modifications. However, it does not directly contrast with siblings like devicelens_explain_device for when to use this vs. other tools.

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