capture_screenshot

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Take a screenshot' implies a non-destructive read operation, but it does not explain what happens to the image (e.g., saved to disk, returned as base64), whether it blocks until complete, or how the wait_for_render parameter affects the outcome. This is a significant gap for an agent invoking the tool.

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, front-loaded sentence with no unnecessary words. It conveys the core action efficiently and is 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?

With no output schema and no annotations, the description leaves out critical details such as return format, file saving behavior, and potential side effects. For a tool with four parameters and a rendering wait option, more context is needed for an agent to fully understand the tool's impact and output.

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 describes all four parameters (method, region, filename, wait_for_render) with clear descriptions, giving 100% coverage. The tool description adds no additional meaning beyond the schema, so the baseline of 3 is appropriate.

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 'take' with a clear resource 'screenshot of the TradingView chart'. It clearly distinguishes from sibling tools like chart_get_state (state reading) and chart_vision_read (visual analysis), which are not capture tools.

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 makes the intended usage obvious: use this tool to capture a chart screenshot. No exclusions or alternatives are mentioned, but since no other sibling tool serves this exact purpose, the context is clear enough for selection.

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