herdr_app_shotCaptures a running Herdr window's last rendered frame as a PNG, even if the window is covered, and returns the saved file's absolute path.
Save the window's last rendered frame as a PNG (its own rendering, even when covered) and return its absolute path. Needs a running window.
| Name | Required | Description | Default |
|---|---|---|---|
| file | No | Where to save (default: herdr-shot.png in the current folder). |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. It discloses the key traits: captures the window's own last rendered frame even when covered, writes a PNG, returns an absolute path, and requires a running window; it does not cover overwrite behavior or failure modes in detail.
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 compact sentences, front-loaded with the action and result, and the precondition is appended without waste.
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?
The tool is simple, has a fully documented single optional parameter, and no output schema. The description supplies the return path and running-window requirement, leaving no material gap for correct invocation.
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?
The only parameter, file, is fully documented in the schema (100% coverage), including the default. The description does not add file-path semantics beyond the schema, so it meets the baseline for high schema coverage.
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 ('Save') and resource ('window's last rendered frame as a PNG'), including the return value (absolute path). The 'even when covered' detail further clarifies what is captured, making it unmistakable versus other window/app siblings.
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 a precondition ('Needs a running window') but gives no explicit when-to-use guidance or alternatives among the many herdr_app_* siblings. The context is implied for visual capture, but selection guidance is thin.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.