capture_desktop

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

No annotations are provided, so the description carries the full burden. It does disclose a meaningful behavioral trait — that the capture happens at the OS level and does not run inside houdini-bin — but says nothing about resolution, output format, or where the file lands when output_path is omitted.

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 with the scoping and alternative front-loaded; minimal waste. The parenthetical 'does not run inside houdini-bin' is a bit awkwardly placed but informative.

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?

An output schema exists, so return values need not be explained, and the when-to-use/alternative guidance is present. However, the sole parameter (output_path) is undocumented and the description omits output location/format details an agent needs to call it 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% and the description never mentions output_path, so it adds no meaning beyond the bare parameter name. For a single param at 0% coverage, the description should compensate and does not.

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+resource (grab the Houdini window from the OS) and explicitly differentiates from the sibling capture_screenshot, which an agent could otherwise confuse it with. Slightly ambiguous whether 'desktop' means the full screen or just the window, but the intent is clear.

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?

Gives an explicit use case ('verify network editor / UI') and names the alternative with the condition that selects it ('viewport beauty should use capture_screenshot instead'), so the agent knows when to route elsewhere. No exclusions beyond that binary split, but the primary routing decision is covered.

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