godot_screenshot

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

The description discloses auto-rotation behavior (keeps last 50, deletes older than 24h) and cleanup action, which is valuable beyond the bare schema. However, it does not describe the return value or potential side effects (e.g., blocking).

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 dense and packs a lot of information into a single sentence, but it uses abbreviations and compact notation that may require careful parsing. It is efficient but slightly less readable.

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 minimal schema, the description covers all actions, their parameters, and cleanup behavior. However, it omits the output structure and does not clarify whether any parameters are required beyond action.

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 0% schema description coverage, the description fully compensates by listing all actions and their optional parameters (e.g., game(max_width?,format?,quality?)). This provides semantic meaning that the input schema lacks.

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 that the tool is for taking screenshots and saving them to disk, with multiple action types (game, editor, region, burst, cleanup). It is distinct from all sibling tools, none of which handle screenshots.

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 explicit comparison to alternatives or when-not-to-use guidance is given. However, since this is the only screenshot tool among siblings, usage context is implied but not formally stated.

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