godot_capture_viewport

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description has a lower burden. It adds the context of high-resolution capture and AI inspection, but it does not describe whether the default response includes base64, whether a file is saved, or how output is delivered beyond relying on the output schema.

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 one focused, brief sentence that communicates the core action and purpose with no wasted words. It is appropriately short for a tool that also has a rich schema and output schema.

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 the annotations, output schema, and the detailed parameter schema, the definition is largely complete for an agent to use the tool. The only notable gap is that it does not explicitly advise when to choose this over godot_take_screenshot or tell the caller to enable include_base64 when AI vision processing is required.

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 schema itself documents all five parameters with defaults and descriptions, so the description does not need to repeat them. The description's 'high-resolution' and 'AI Vision' wording loosely maps to max_width/max_height and include_base64, but it adds no parameter-level details beyond the schema.

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 identifies a specific verb and resource: capturing a high-resolution viewport frame for AI Vision inspection. It does not explicitly distinguish itself from the sibling tool godot_take_screenshot, but the 'viewport frame' and AI-inspection framing provide reasonable differentiation.

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 phrase 'for AI Vision inspection' implies an intended use case, but the description gives no explicit when-to-use versus godot_take_screenshot guidance and no exclusions. An agent can infer usage, but the tool does not help disambiguate between its capture siblings.

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