CreateScanDocument

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

No annotations are present, so the description carries the full burden of behavioral disclosure. It implies a write operation and OCR processing but does not describe permissions, reversibility, what OCR does to the document, or what the response looks like. This is minimal and insufficient for a mutation tool.

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 very short with no filler, but it is so terse it borders on under-specification. It offers a fragment rather than a structured explanation, so while concise, it does not fully serve its purpose.

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 output schema, no annotations, and a large sibling set, the description fails to explain what happens after creation/OCR, what is returned, or how this tool fits into the broader document workflow. An agent cannot confidently select this tool based on the provided context.

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?

The input schema is empty with zero parameters, so the schema already covers everything. The description adds no parameter details, but none are needed. Baseline for zero parameters is met.

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 the action ('Create and OCR') and the resource ('Scan Document'), which is more specific than a tautology. However, it does not explain what a Scan Document is or how it differs from the generic CreateDocument sibling, leaving the purpose somewhat ambiguous.

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?

No guidance is provided on when to use this tool versus CreateDocument, UpdateScanDocument, or any of the other document-related siblings. There are no conditions, prerequisites, or exclusions.

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