wpf_capture_screenshot

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

No annotations provided so description bears full burden. It discloses that 'render' re-renders off-screen and cannot see popups/menus, while 'screen' captures on-screen pixels and requires visibility. This is good behavioral disclosure for a screenshot 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?

Two sentences: first states purpose concisely, second provides detailed mode guidance. Efficient but could be slightly more structured with bullet points for clarity. No information is wasted.

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?

No output schema, but description notes it returns an image for visual analysis. Parameters are mostly covered. For a screenshot tool with no complex outputs, this is complete enough for an agent to use correctly.

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 description compensates by explaining 'element_handle' (capture specific element or omit for entire window) and 'mode' (render vs screen with behavioral differences). max_width and max_height are not explained beyond defaults, but their purpose is somewhat implied.

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?

Clearly states 'Capture a screenshot of the WPF window or a specific element.' The verb 'capture' and resource 'screenshot of WPF window/element' are specifically defined. No sibling tool performs a similar function, so it is well-differentiated.

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?

Provides explicit guidance on when to use each mode: 'render' for general use but cannot capture popups/menus; 'screen' for capturing popups/menus after clicking. Also advises to use element_handle for specific elements. Lacks explicit 'when not to use' but is clear enough.

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