browser_screenshot

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

With no annotations, the description carries the behavioral disclosure burden. It clearly states the side effect (a PNG is saved to data/screenshots) and implies that a path is produced for subsequent use. It doesn't cover overwriting, file naming, or page-load requirements, but the core behavior is transparent.

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 entire description is one efficient sentence with no filler. It front-loads the key fact (save a PNG to data/screenshots) and closes with the actionable next step.

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 two-optional-parameter tool, the essential flow is covered: save, get path, pass to record_application. But the description leaves `full_page` and `name` semantics unaddressed, and there is no output schema to fill that gap, so the definition is only partially complete.

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 0%, so the description must compensate, but it never explains `name` or `full_page`. The mention of `path` is about the output rather than the parameters, so the agent gets little help understanding the optional arguments.

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 states a clear verb and resource: save a PNG to data/screenshots. It also explains the intended downstream use (pass the path to record_application). However, it does not explicitly differentiate itself from sibling tools like browser_snapshot or browser_upload.

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?

It gives a concrete usage context: capture a screenshot and use the saved path as evidence for record_application. This is clear context, but it stops short of explicitly saying when not to use it or naming alternative tools.

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