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

Discloses key behaviors: interactive widget, local processing (never uploaded), optional signature_name for pre-rendered signature. No annotations provided, but description covers core aspects. Lacks mention of return value or error conditions, but sufficient for the interactive nature.

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?

Front-loaded with key information in English, followed by Polish translation. Could be more concise by omitting duplicate translation, but still efficient and clear.

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 an interactive signing tool with no output schema, the description provides sufficient context: widget behavior, local processing, optional parameter. Lacks details on return value or edge cases, but adequate for the task.

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 100%, so baseline is 3. The description reiterates the schema's detail for signature_name but adds no new meaning. File parameter is mentioned briefly.

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?

Clearly states it opens an interactive widget for PDF signing, with specific actions (draw, type, upload). Distinct from sibling tools like fill_pdf_form, merge_pdfs, and split_pdf.

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?

Explicitly instructs to 'ALWAYS use this for PDF signing requests' and warns not to sign or modify the PDF directly, providing clear guidance on when to use this tool vs alternatives.

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