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

Since no annotations are provided, the description carries the full burden of behavioral disclosure. It states that the PDF reflects the document as it currently exists in the session (after applied proposals or as opened), and discloses the link's 24-hour validity and the inclusion of page count. It doesn't mention potential side effects, but as a rendering/export operation, side effects are unlikely. The description provides sufficient transparency for a read-like operation.

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 core action and output stated first, followed by a clear scope exclusion and alternative. Every sentence contributes essential information, and the structure is front-loaded with the primary purpose, making it efficient and 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?

For a simple, parameterless tool, the description is complete: it covers purpose, output details (PDF link, validity, page count), scope (current session's cabin), and the alternative for workbooks. There is no output schema to document, and no other operational details (like authentication or rate limits) are necessary for this type of export. An agent can confidently invoke this tool based on the description alone.

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 tool has zero parameters, so the description correctly avoids parameter-specific details. Per the baseline rule for 0-parameter tools, a score of 4 is appropriate because there is no parameter semantics to add, and the description does not clutter with irrelevant information.

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 tool's function: it lays out the document's current state and returns a PDF download link plus page count. It uses specific verbs ('lay out', 'return') and identifies the resource (document), and it distinguishes itself from the sibling tool for workbooks ('for workbooks use document_save_copy'), making its purpose unambiguous.

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 explicitly states when to use this tool (for documents needing PDF export) and when not to use it (for workbooks), directing to the specific alternative (document_save_copy). This provides clear guidance without ambiguity.

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