jotify_upload_batch

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 transparency. It mentions returning a media list but does not disclose side effects such as whether uploads are permanent, if partial failures are possible, or authentication requirements, leaving a significant transparency gap.

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 entire description is one sentence that front-loads the key action ('一次性批量上传') and outcome ('返回已上传的媒体列表'). Some redundancy exists between '一次性' and '批量', but it remains concise and free of waste.

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?

For a tool with no output schema and no annotations, the description provides the core use case and return value, but leaves questions about parameter interaction (e.g., 'items' vs 'filePaths') and error handling unanswered. The moderate complexity of three parameters and one enum warrants slightly more context than provided.

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 coverage is 100% according to context signals, with all three parameters described in the schema (e.g., '业务用途' and '待上传的媒体数组'). The description adds minimal parameter-specific value beyond the schema, but the schema itself is self-sufficient, so a baseline of 3 is appropriate.

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 uses the specific verb '批量上传' (batch upload) with clear resources ('多张图片或音视频') and states it returns a media list for posting ('返回已上传的媒体列表供发帖使用'). This clearly differentiates from the sibling single-upload tool 'jotify_upload_media' by emphasizing the batch and turn-saving nature.

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 phrase '极大减少交互轮次' (greatly reduces interaction turns) implies a recommended use case for batch uploads rather than repeated single uploads. However, it does not explicitly name alternatives or state when not to use it, so guidance is implied rather than explicit.

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