Print document

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

With no annotations, the description carries the full behavioral disclosure burden. It covers conversion of .docx to PDF, caching next to the docx, default printer usage, and the important distinction that confirmation only means the job was sent, not physically printed. This is rich, specific behavioral information.

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?

Three sentences, each earning its place. Front-loaded with the core action, then key details on file handling and printing behavior. No redundant or vague wording.

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 simplicity (2 parameters, no output schema), the description covers essential aspects: file names, format conversion, printer selection, and confirmation semantics. It lacks details about error handling or return format, but these are less critical for a straightforward print action.

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 has 100% coverage, so parameters are already documented. The description goes beyond by explaining the Resumes folder shortcut, full path support, PDF vs .docx handling, and the default behavior of the printer_name parameter. This adds meaningful practical context.

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 specific action: 'Silently print a saved document to a printer.' It identifies the resource (saved document) and distinguishes from sibling tools like save_document, read_document, and delete_document by focusing on the print operation.

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 gives clear context for usage: it mentions saved documents, file names in the Resumes folder or full paths, and default printer behavior. While it doesn't explicitly state when not to use it or name alternatives, the context is unambiguous enough for an agent to choose this tool for printing tasks.

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