save_pdf

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

There are no annotations, so the description carries the full burden of behavioral disclosure. It only states the basic action without any side effects, limitations, performance considerations, or failure modes. For instance, it doesn't indicate whether JavaScript rendering is involved or whether the output is a binary file, making the tool's behavior opaque.

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, concise sentence that immediately conveys the primary action without any wasted words. It is well-structured and front-loaded, making it 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?

Given the tool's moderate complexity (3 parameters, one with a default, and an output schema), the description is too sparse. It doesn't address the timeout_profile parameter or mention any prerequisites for the URL (e.g., must be publicly accessible). It also lacks context on when to use this tool over siblings like download_file, making it incomplete for reliable selection and invocation.

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 has 3 parameters with 0% description coverage, and the description adds no meaning beyond the parameter names. It doesn't explain what 'path' refers to, what values are valid for 'timeout_profile', or how they relate to the PDF generation. The description fails to compensate for the lack of schema documentation.

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 clear verb 'Save' and a specific object 'URL as a PDF file', which unambiguously identifies the core function. It is distinct in its clarity, but it doesn't explicitly differentiate from sibling tools like download_file or screenshot, so it doesn't reach a 5.

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 no guidance on when to use this tool versus alternatives such as download_file, screenshot, or scrape_url. There are no prerequisites, use cases, or exclusions mentioned, leaving the agent without direction for selecting the appropriate tool.

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