capture_screenshot

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

With no annotations, the description must disclose side effects and runtime behavior. It mentions saving a PNG, but does not clarify whether the render is offscreen, whether the project must be running, how output paths are resolved, or what happens if the scene fails to load. The 'controlled viewport' phrase hints at non-interactive rendering but lacks 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?

The description is a single sentence with no filler, which is efficient. However, the brevity comes at the cost of missing critical details, making it under-specification rather than well-structured conciseness. The sentence order is logical but leaves too much unsaid.

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 has five parameters, no annotations, and no output schema, so the description bears full responsibility for explaining usage. It only covers the basic purpose and output format, omitting return values, error cases, output path default behavior, and interaction with the Godot project. This is inadequate for a tool with this complexity.

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 only 20% (only projectPath has a description). The description does not explain the meaning of width, height, scenePath, or outputPath beyond generic terms like 'viewport' and 'PNG'. It provides no additional detail about parameter defaults or relationships, leaving the agent to infer from names.

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 clearly states the action ('Render a scene') and the outcome ('save a PNG inside the project'), which matches the tool name. It distinguishes from sibling tools like inspect_scene_tree or create_scene by focusing on image capture rather than scene editing or inspection, though it doesn't explicitly name alternatives.

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?

No guidance is provided on when to use this tool versus other rendering or screenshot tools. There are no prerequisites, no mention of required project state, and no exclusions or alternatives mentioned.

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