add_text_stamp_to_pdf

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

With no annotations, the description carries the full burden of behavioral disclosure. It states the operation 'Saves the stamped PDF to disk' and references the API field isItalics, offering some transparency. However, it does not clarify whether the original PDF is modified or a new file is created, nor does it mention permissions, rate limits, or side effects. This is a moderate gap for a write 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 concise and well-structured. Three sentences cover the purpose, key parameters, and output behavior. The example for pages ('all, 1, 1-3') is practical. No redundancy or filler—every sentence earns its place.

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 complexity (24 parameters, no annotations, no output schema), the description is insufficiently complete. It does not explain how the output file is named/determined, what the function returns, or any prerequisites (e.g., API key). It also fails to mention many parameters, leaving the agent to guess their semantics. A more comprehensive description is needed for this complexity.

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 coverage is 0%, so the description must compensate. It names key parameters like pdf_file_path, stamp text (presumably 'text'), pages, alignX/alignY, font and margin settings, giving some meaning beyond the schema. However, it uses informal names (alignX/alignY instead of align_x/align_y) and leaves many parameters (rotate, opacity, transverse, etc.) completely unexplained. Partial compensation, but far from complete.

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: 'Add a text stamp or watermark to a PDF.' It specifies the resource (PDF) and the action (adding text), and distinguishes it from sibling tools like add_image_stamp_to_pdf and add_text_watermark_to_image by the 'PDF' and 'text' qualifiers. Mentioning the underlying API endpoint adds specificity without ambiguity.

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 clear context for when to use the tool: it is for adding text stamps/watermarks to PDFs, with an example of pages syntax. It does not explicitly name alternatives or exclusions, but the context is specific enough that an agent can infer it applies to PDF text stamping rather than image stamping or other formats.

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