upload_capture

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

With no annotations provided, the description carries full burden and does well. It discloses multiple behavioral traits: the multi-step processing pipeline (OCR, parsing, extraction, storage, copying, connection detection), the overwrite behavior controlled by the force parameter, and the return format (summary with strongest connection). It doesn't mention error handling, rate limits, or authentication needs.

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 perfectly structured and concise. First sentence states the comprehensive purpose, followed by clearly labeled Args and Returns sections. Every sentence earns its place by providing essential information without redundancy.

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 (multi-step processing pipeline), no annotations, and the presence of an output schema (which handles return values), the description is complete enough. It covers purpose, parameters, behavior, and return summary, providing all necessary context for an agent to use this tool effectively.

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 0%, so the description must compensate fully. It provides excellent parameter semantics: image_path is explained as 'Absolute path to the image file (JPG, PNG, TIFF, etc.)' and force as 'Set to True to overwrite an existing capture with the same template ID (default False — warns instead).' This adds crucial meaning beyond the bare schema.

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's purpose with specific verbs (process, run OCR, parse, extract, store, copy, detect) and resources (journal page photo, capture, knowledge base). It distinguishes from siblings like bulk_upload (batch vs single) and find_connections (detection only vs full processing).

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 provides clear context for when to use this tool (processing a single journal page photo for OCR and storage). It doesn't explicitly mention when not to use it or name alternatives, though bulk_upload is an obvious sibling for batch processing. The force parameter guidance implies usage for overwriting existing captures.

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