Export PDF

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

readOnlyHint=true already tells the agent this is a safe, non-mutating operation, so the description's job is lighter. It usefully adds that only the current page is captured and where the file lands, but it does not say whether the artifact path is returned, whether the export blocks on rendering, or that it creates a file on disk (a side effect the readOnly annotation does not advertise). Not a hard contradiction, since no existing state is modified, but worth noting.

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?

A single front-loaded sentence with no filler; the verb and destination come first. It is efficient, though it spends its one sentence on mechanics rather than on the guidance an agent would actually need.

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?

Four undocumented parameters, no output schema, and no statement of what the tool returns (path? filename? nothing?), so the agent cannot tell how to locate the produced file. For a tool whose entire value is producing an artifact, the description leaves the most important details unspecified.

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 description coverage is 0% and all four parameters (path, format, landscape, print_background) are undocumented. The description only gestures at the artifact directory, giving no meaning for the format enum, no default page size, orientation, or background-printing behavior. With zero coverage, the description should have compensated and does not.

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?

States a concrete verb pair ('Render ... and save') and a concrete resource ('the current page'), plus the output format (PDF) and destination ('artifact directory'). That is enough to separate it from sibling capture tools such as 'screenshot' or 'markdown', though the description never names them explicitly.

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?

There is no statement of when this tool should be chosen over 'screenshot' or 'markdown', and no prerequisites are given (e.g. must a page be open, does it wait for rendering to finish, what happens if a previous export exists). The phrase 'current page' only weakly implies a page must be loaded.

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