UpdateScanDocument

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

The description implies a multi-step behavior ('update' plus 'OCR') but does not explain effects, prerequisites, or side effects. With no annotations provided, the description carries full burden and fails to disclose what happens during OCR or update processes.

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 extremely short, but it reads as a fragmented phrase rather than a coherent sentence. It lacks structure and does not earn its place by adding meaningful information beyond the tool's name.

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 no annotations, no output schema, and a description that is essentially a restatement of the name, the tool is completely underspecified. An agent cannot know what inputs are expected, what the tool does functionally, or what it returns.

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?

There are zero parameters, so the schema requires no documentation. The description's mention of 'Update and OCR' gives some minimal hint of the tool's operation, but since there are no parameters to explain, the baseline of 4 applies.

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 reads as a series of fragments—'Update and OCR Scan Document'—which lacks a clear verb+resource statement. It does not specify what exactly is updated or how OCR is applied, and it does not distinguish this tool from siblings like UpdateScanDocument or QueryDocument. It is effectively a tautology of the tool's name.

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?

There is no guidance about when to use this tool versus alternatives such as CreateScanDocument, UpdateDocument, or QueryDocument. Without any context, an agent cannot determine the appropriate conditions for selecting this tool.

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