get_screenshot

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

With no annotations provided, the description carries full burden. It clearly states the tool does not capture a new image (read-only retrieval), specifies the return format including success, url, and screenshot_path. It lacks details on error conditions or path existence, but the core behavioral traits are well-disclosed.

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?

Two sentences: first states purpose and return, second gives usage guidance and disambiguation. Every word is informative and necessary. No filler or redundancy.

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?

For a simple tool with 2 parameters and no output schema, the description covers purpose, return structure, usage context (must be previously tested), and disambiguation. It is fully adequate for an agent to select and invoke the tool 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 description coverage is 100%, so the schema already provides basic descriptions. The description adds value by relating parameters to the prerequisite test_url/test_project process, providing context beyond the schema. This helps the agent understand that the URL must have been tested previously.

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 gets the saved screenshot file path for a previously tested URL in a project. It uses a specific verb 'Get' and resource 'saved screenshot file path', and distinguishes itself from sibling tool screenshot_session by explicitly noting it does not capture a new image.

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 provides explicit usage guidance: use this after test_url/test_project to retrieve the screenshot, and use screenshot_session instead for capturing a new image. This clearly tells when and when not to use the tool, and names the alternative.

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