bulk_upload

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively describes key behaviors: processing multiple images in batch, skipping non-image files silently, handling duplicates with warnings by default, and returning a summary table. It doesn't mention potential rate limits, authentication requirements, or error handling for invalid paths.

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 well-structured and appropriately sized. It begins with the core purpose, then explains the processing behavior, provides clear parameter documentation, and ends with the return value. Every sentence adds essential information with zero wasted content.

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 (batch processing with file type filtering and duplicate handling), no annotations, and the presence of an output schema, the description is remarkably complete. It explains what the tool does, how it behaves, what parameters mean, and what it returns, making the output schema's details about the 'summary table' sufficient.

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 description adds significant value beyond the input schema, which has 0% description coverage. It clearly explains both parameters: 'folder_path' as 'Absolute path to the folder containing journal photos' and 'force' with detailed behavior about overwriting existing captures vs. skipping duplicates with warnings. This fully compensates for the schema's lack of descriptions.

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 all journal page photos', 'Finds every image file', 'runs the full upload pipeline') and identifies the resource ('in a folder at once'). It distinguishes this bulk operation from the sibling 'upload_capture' tool which likely handles single uploads.

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 about when to use this tool ('Process all journal page photos in a folder at once') and what it does with non-image files. However, it doesn't explicitly state when NOT to use it or mention alternatives like the 'upload_capture' sibling tool for single uploads.

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