upload_file

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions the base64 encoding requirement but does not disclose overwrite behavior, permission requirements, file size limits, or response shape, which are relevant for a mutating upload operation.

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 a single, front-loaded sentence with no filler. It captures the essential operation and the critical encoding detail while remaining compact.

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?

The request parameters are fully documented by the schema, making the invocation inputs clear. However, the absence of an output schema and the lack of behavioral context such as overwrite semantics or access requirements leave noticeable gaps for an upload operation.

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% with descriptive text for all three parameters, so the baseline is 3. The description only restates the base64 content requirement already present in the content parameter description, adding no new semantic meaning.

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 a specific verb and resource: 'Upload a file to Bitrix24 disk folder.' This clearly differentiates the tool from all sibling tools, which deal with deals, contacts, tasks, users, and messages rather than file 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 intended use is implied by the operation name and resource, but the description provides no explicit when-to-use guidance or exclusions. There are no file-related sibling tools to confuse it with, so the implied context is sufficient but not elaborated.

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