wpf_attach

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

No annotations are provided, so the description must fully disclose behavior. It mentions auto_inject for injecting the Inspector but does not disclose side effects on the target process, error conditions, or prerequisites (e.g., administrator rights, Inspector installation). The description lacks sufficient behavioral context.

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 consists of two sentences: the first states the core purpose, and the second adds essential parameter guidance. It is front-loaded, concise, and contains no filler content.

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 three parameters and no output schema, the description covers the main action and parameter semantics but does not address what happens after attachment (e.g., return value, readiness for other tools). It omits the context that this tool is a prerequisite for most other WPF tools, which would be valuable for the agent.

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 clarifies the purpose of process_id and process_name as identification methods and explains auto_inject for injection. However, it does not address scenarios like both identifiers provided, the default behavior of null, or the difference between the two parameters in terms of precedence.

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 ('Attach'), the target ('WPF application'), and the two identification methods ('process ID or name'). This distinguishes it from sibling tools like wpf_click_element or wpf_capture_screenshot, which operate on an already-attached application.

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 guidance on when to set auto_inject=true, but does not explain when this tool should be used versus alternatives (e.g., wpf_list_processes as a prerequisite). No explicit when-not-to-use or context for choosing between process_id and process_name.

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