wavexis_screenshot

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, destructiveHint=false. The description adds that the tool returns JSON with base64 or file path and accepts screenshot parameters. This is useful but doesn't enrich the behavioral profile beyond what annotations provide.

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 two sentences with no fluff. It quickly states the core action, describes the input argument, and mentions the return format.

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?

The description covers the basic purpose and return type. However, given the tool's complexity (many optional parameters like session_id, wait strategies) and the existence of an output schema, the description could add context like usage with an existing browser session or the ability to capture a specific element. It is minimally 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?

The input schema has detailed descriptions for each parameter (URL, selector, format, etc.), so schema description coverage is effectively high. The description's mention of 'URL, selector, format, etc.' adds no new meaning. Baseline 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 clearly states the tool takes a screenshot of a web page or element. It uses a specific verb ('Take') and resource ('screenshot'), distinguishing it from siblings that scrape, print PDFs, or perform other actions.

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 guidance on when to use this tool vs alternatives. With many sibling tools (e.g., wavexis_scrape, wavexis_pdf, wavexis_dom_snapshot), the description does not help the agent decide which tool is appropriate for a given task.

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