add_form_fields

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

With no annotations, the description carries the transparency burden. It explains the two mechanisms for adding fields (placeholder tags and explicit positions), which is useful, but it does not disclose mutation semantics—such as whether existing fields are replaced, versioning behavior, or required permissions. The description adds partial context beyond the schema but leaves key behavioral details unspecified.

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 that efficiently captures the core action and the two modes of operation. There is no redundant wording, and every clause contributes meaningful information.

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 (nested objects for fields and overrides, no output schema, no annotations), the description covers the main use cases but does not mention result behavior or side effects. The parameter-rich schema compensates for many details, making the description adequately complete for a focused tool description, though it could be slightly more explicit about the outcome.

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%, so the baseline is 3. The description adds value by clarifying that fieldOverrides refine placeholder tags, which is not obvious from the schema's generic 'Per-field overrides keyed by field name' description. It also aligns the 'fields' parameter with 'explicitly positioned fields', enhancing understanding beyond raw schema definitions.

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 adds interactive form fields to a stored PDF, using a specific verb ('Add') and resource ('stored PDF'). It also distinguishes two modes: from placeholder tags refined via fieldOverrides and explicitly positioned fields, which separates it from sibling tools like extract_form_data or flatten_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?

The description conveys clear context for when to use this tool—when adding form fields to a PDF—by outlining the two supported input methods. It does not explicitly name alternatives or state when not to use it, but the purpose is unambiguous given the sibling tool names.

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