qt_get_property

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

With no annotations provided, the description carries the full burden. It discloses read-only behavior, no side effects, and the notable rejection of hidden, disabled, and zero-size elements—even for reads. This goes beyond the schema and helps prevent common errors.

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 primary purpose. The second sentence adds a crucial behavioral note without wordiness. Every sentence 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 simple read operation with an output schema, the description is adequately complete. It covers the principal behavior and the critical visibility constraint. It does not enumerate property names, but the existence of an output schema reduces the need to explain return values.

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 adds some meaning by implying 'name' is the property to read and that 'element_id' must be from a recent find/snapshot, but it does not explicitly define session_id or enumerate valid property names. The parameter clarification is thin.

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 action ('Read a property from a UI element') with a specific verb and resource. This distinguishes it from siblings like qt_set_property, which performs the opposite operation.

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 provides clear context: it is read-only, and it specifies a prerequisite that the element id must come from a recent find/snapshot of a visible element. It does not explicitly name alternatives, but the sibling list and the read/write contrast imply when to use vs. qt_set_property.

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