Embed LTV validation material (PAdES B-LT)

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

The description discloses important behavioral traits beyond annotations: network behaviour via the OPERATOR revocation provider, zero network in offline mode, incremental merging of existing /DSS, and constraints on signed/unencrypted input. There is no contradiction with the annotations, which treat it as a mutating and world-open 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 dense but efficient: it front-loads the core purpose and PAdES context, then uses compact parentheticals for mode/error details. It avoids fluff while still packing workflow, security, and environmental constraints into a text that earns its length.

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 complex, 9-parameter tool with external network side effects, this description is complete. It explains the PAdES level, the call sequence, the mode differences, the security configuration, the offline/online material sources, and the key input constraints. Combined with the full schema and present output schema, an agent has enough to invoke it correctly.

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%, and each parameter already has detailed inline descriptions. The description adds some contextual value about modes and prerequisites, but it largely restates information present in the input schema rather than contributing new parameter-level semantics.

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 states a specific verb-resource pair: 'embed a Document Security Store (/DSS + per-signature /VRI)' with validation material. It also situates the tool in a clear sequence (sign_pdf → add_ltv → timestamp_pdf), which disambiguates it from sign_pdf and timestamp_pdf without needing to inspect the schema.

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?

Usage context is explicit: it is ladder step 3, requires at least one signed signature, requires an unencrypted PDF, and differentiates online vs offline modes. It even names the error condition (REVOCATION_NOT_CONFIGURED) and the environment prerequisites, leaving no ambiguity about when this tool is appropriate.

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