get_editor_screenshot

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

The description discloses two key behavioral traits: empty save_path returns base64 and non-empty writes to disk. This is important because it reveals the output mode and file system side effect without relying on annotations. It does not detail the exact structure of the returned base64, but that is a minor gap.

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 fits in a single sentence, starting with the action and then providing a clean conditional clause. Every word serves a purpose, making it highly concise and easy to parse.

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?

For a simple one-parameter tool with no output schema, the description covers the essential decision logic (base64 vs file) and identifies the target (editor window). A clearer statement about the exact return format of the base64 would improve completeness, but overall it is adequate for successful 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?

With schema description coverage at 0%, the description successfully explains the sole parameter's role: save_path controls whether the screenshot is returned inline or written to disk. This adds essential meaning beyond the raw schema definition, though it could specify path format requirements.

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 uses a specific verb 'Capture' and clearly states the resource: 'PNG screenshot of the Godot editor window'. This distinguishes it from sibling tools like get_game_screenshot, which target the game view, making the purpose unambiguous.

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 context is implied from the phrase 'editor window', which suggests using this tool when an editor screenshot is needed. However, it does not explicitly name alternatives or state when not to use it, leaving some ambiguity in tool selection.

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