list_pdf_document_signer_placeholders

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

With no annotations, the description carries full burden. It conveys a read-only operation ('Lista') but does not mention side effects, auth requirements, rate limits, or return format. The behavior is minimally transparent beyond the name.

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, front-loaded sentence with a clear verb and resource. Every word is purposeful. Slightly more structure could be added, but it is efficient.

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 simple nature of the tool (list, two required parameters, no output schema), the description is complete enough for an agent to understand its purpose and differentiate from siblings. It could mention return format but is adequate.

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 coverage is 100% with both parameters described by name only. The description adds 'specific signer' but no extra semantics beyond the schema. Baseline score is appropriate.

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 verb 'List' and the resource 'placeholder/campi di firma di un signer specifico su un PDF'. It distinguishes from sibling tools like list_pdf_document_placeholders (all placeholders) and list_pdf_document_signers (just signers), making the specific scope evident.

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 implies use when needing placeholders for a specific signer, but does not explicitly state when to use this tool over alternatives, nor does it provide any exclusion criteria. It lacks explicit guidance on context.

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