take_screenshot_with_context

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

No annotations are provided, so the description carries full burden. It states the tool takes a screenshot with metadata, but does not disclose behavioral traits such as whether it is read-only, where the screenshot is saved, or if it modifies the scene. Important details like file format and side effects are missing.

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 concise sentence that conveys the core function and expected output. No unnecessary words, front-loaded with the primary action.

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 absence of annotations and output schema, the description lacks important details such as output format (file?), mutability, and precise behavior of the metadata. For a tool with 3 parameters that likely produces a file, more context is needed for the agent to use it correctly.

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 coverage is 100%, so the description adds limited value beyond the schema. It explains that 'include_nodes' and 'include_props' relate to property snapshots within the context metadata, which is helpful but not extensive. Baseline 3 is appropriate as the schema already documents each parameter.

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 tool takes a screenshot with scene context metadata, including node tree and property data. It specifies the verb 'Take' and resource 'screenshot with context', which distinguishes it from sibling tools like get_game_screenshot or capture_frames that lack metadata.

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 description implies the tool is for screenshots needing context metadata, but does not explicitly state when to use this vs alternatives (e.g., get_game_screenshot for plain screenshots). No when-not or alternative guidance is provided, leaving the agent to infer usage.

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