extract_pdf_document_parties

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

No annotations are provided, so the description bears the full burden of behavioral disclosure. It mentions combining metadata from registered signers with text extraction, which suggests read-only analysis, but does not explicitly state whether the tool modifies state, requires permissions, or has rate limits. The absence of destructive/read-only hints is a gap.

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 a single sentence but packs substantial information (data fields, source, context). It is efficient and well-structured, though the sentence is somewhat long. No extraneous content.

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 moderate complexity, no output schema, and no annotations, the description provides enough context by enumerating extracted data fields and noting optimization for Italian contracts. It covers the essential behavioral aspects, though it could benefit from mentioning whether results include confidence scores or are only from text.

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 the baseline is 3. The description does not add parameter-specific details beyond the schema; it only summarizes overall output. Since schema already documents each parameter, the description adds limited extra semantic value.

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 extracts anagraphic data of parties from a PDF, listing specific data fields (codice fiscale, P.IVA, etc.) and noting optimization for Italian contracts. This is a specific verb+resource and distinguishes it from siblings like 'extract_heu_document_parties' by targeting PDF documents.

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 explains what the tool does but does not provide any guidance on when to use it versus alternatives (e.g., 'extract_heu_document_parties') or when not to use it. Usage context is implied from the purpose, but no explicit exclusions or prerequisites are given.

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