save_pdf

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

Since no annotations are provided, the description must carry the behavioral burden. It does disclose a key behavior: the document remains in memory and can be modified after saving. But it omits other potentially relevant details such as whether the file will be overwritten, permission requirements, or error behaviors. This adds some transparency but not a rich behavioral picture.

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 the primary action front-loaded and the second sentence providing valuable behavioral context. There is no redundancy or filler, making it concise and well-structured.

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 narrowly scoped save operation with two well-documented parameters and an output schema, the description covers the essential information for selection and invocation. It could mention overwrite behavior or error handling, but such details are not critical for the tool's basic use. Overall, it is sufficiently 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 already fully documents both parameters with clear descriptions (document_id and output_path), and schema coverage is 100%. The description adds no additional parameter-level information, so the baseline score of 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 uses a specific verb 'Save' with the resource 'in-memory PDF document' and destination 'disk', clearly distinguishing it from sibling tools like load_pdf, close_pdf, or redact functions. The phrase 'in-memory' also clarifies that the document must already be loaded, which is a distinct context.

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 clearly implies when to use the tool: when you have an in-memory PDF document and want to persist it to disk. It notes that the document remains loaded after saving, which implicitly contrasts with close_pdf. However, it does not explicitly name alternatives or state when not to use it, so it falls short of a 5.

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