wavexis_pdf

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

The description contradicts annotations: annotations mark readOnlyHint=true and destructiveHint=false, but description reports side effects like writing to output_path, launching browser, and navigating. This is a clear contradiction.

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 concise, well-structured with clear sections, no redundant text, and immediately states the purpose.

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?

Covers core behavior, side effects, and return format. Lacks session management context, but annotations and schema partially fill gaps.

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 description mentions key parameters (url, js, output_path) and their roles, but does not cover all parameters (e.g., media, paper, margin). Given schema description coverage is 0% (contradicted by actual schema), description partially compensates.

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 it generates a PDF from a web page, and distinguishes between 'wavexis_screenshot' and 'wavexis_page_pdf' for image capture or pixel-level control.

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?

Explicitly advises when to use alternatives ('wavexis_screenshot' for images, 'wavexis_page_pdf' for pixel-level control) and lists side effects, guiding appropriate usage.

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