capture_screenshot

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

With no annotations, the description carries the full burden of behavioral disclosure. It states the side effect (file written to disk only), how to inspect it (open output_path), and the non-blocking wait behavior of settle_seconds. It could mention overwrite behavior or return value, but the disclosed traits are genuinely useful and accurate.

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?

Every sentence earns its place: capability, disk-only behavior, alternative guidance, and per-parameter clarifications. It is tight, front-loaded, and free of filler.

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 no annotations and no output schema, this description covers what the tool captures, where the output goes, how to view it, when to avoid it, and all three parameters. Nothing essential is missing 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?

Schema description coverage is 0%, so the description must carry the parameter meaning, and it does: each arg is explained with purpose, behavior, and the 120 cap on settle_seconds. This is far beyond what the bare schema names provide.

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 ('Capture') and resource ('screenshot of the viewport or a specific pane tab'). The phrase 'written to disk only' differentiates it from rendering or network-capture siblings, so an agent can distinguish it without opening the schema.

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?

Explicitly directs the agent to prefer text-based tools (get_geometry_info, get_node_info, get_scene_summary) unless visual confirmation is genuinely needed. Also tells the agent to use settle_seconds instead of a shell sleep, which is concrete and unambiguous.

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