kde_window_inspect

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds the useful scoping constraint that the window must come from the same session, but with no output schema it does not say what inspection returns (properties, geometry, state?), which is a meaningful gap for a read tool.

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?

A single short sentence with zero waste, with the key scoping constraint front-loaded. Nothing is redundant with the name or 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 two-required-parameter read tool with no output schema, the description should convey what 'inspect' yields, since nothing else in the definition does. The session-scoping hint is helpful but leaves the agent guessing about the response shape and about how to source the window UUID.

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 coverage is 50%: 'session' is fully documented in the schema, while 'window_id' has no schema description at all. The description compensates by specifying that window_id is a UUID and must come from the same selected session, meaningfully filling the undocumented half. It doesn't say where to obtain that UUID (e.g., from window_list/find).

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 ('Inspect') and resource ('one window'), which clearly distinguishes it from mutating siblings like kde_window_activate or kde_window_set_geometry. It stops short of distinguishing it from the other read tools (kde_window_list, kde_window_find) or saying what 'inspect' reveals.

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 'from the same selected session' implies a prerequisite (the window ID must belong to the already-selected session), which is genuine usage context. It never states when to prefer this over kde_window_list or kde_window_find, nor when not to use it, so usage is only implied.

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