bates_number_pdf

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

No annotations are provided, so the description must disclose behavioral traits. It fails to mention that the tool modifies PDFs (or creates a new file via output_name), whether the original is preserved, or any destructive implications. For a file-processing tool, this is a significant omission.

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 that front-loads the action and avoids redundancy. It is appropriately concise for the purpose, though the lack of detail is reflected in other dimensions.

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?

With 9 parameters, no annotations, and no output schema, a one-line description is insufficient. It does not explain what the tool returns, whether it modifies the original file, how it handles repeated runs, or any edge cases. The description covers only the basic purpose and leaves critical operational context unaddressed.

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 schema fully documents each parameter. The description adds the conceptual context of 'continuous, zero-padded' but does not provide any additional syntax, defaults, or behavior beyond what the schema already states. Baseline 3 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 uses a specific verb ('Add') and clear resource ('continuous, zero-padded Bates identifiers') with context ('legal and audit document production'). It conveys the tool's unique function compared to simple page numbering, but does not explicitly name or contrast with sibling alternatives.

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 phrase 'for legal and audit document production' implies a use case, but there is no explicit guidance on when to use this tool versus alternatives like page_number or watermark, nor any exclusions. The usage context is implied rather than stated definitively.

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