bulk_upload_files

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 mentions optional filtering and folder uploads but omits critical details such as default upsert behavior, error handling, permission requirements, and whether intermediate folders are created. The schema's parameter descriptions add some context but are not referenced in the tool description.

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 concise at two sentences, each serving a clear purpose: the first states the core capability and optionality, the second elaborates on the two modes. No filler or 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 (6 parameters, 1 required), no output schema, and no annotations, the description is too brief. It does not explain the upload destination (Supabase storage implied by 'bucket'), local file path resolution, return value, or confirmation of success/failure. Users may need to infer significant behavior from parameter names alone.

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 baseline is 3. The description adds value by clarifying the dual mode (individual files vs. folder) and the filtering concept, but does not significantly enhance understanding beyond what the schema already provides for each parameter.

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 identifies the tool's action ('Upload multiple local files to storage') and specifies key capabilities like optional filtering by file type and the ability to upload individual files or entire folders. This distinguishes it from sibling tools such as 'upload_file' (single file) and 'list_files'.

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 implies when to use the tool (for bulk uploads) but does not explicitly state when not to use it or provide guidance on alternatives like 'upload_file' for single files. No prerequisites or limitations are mentioned.

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