Upload Nextcloud file from base64

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

The description notes the transfer size limit, adding context. Annotations already indicate destructiveHint true and readOnlyHint false, but description doesn't contradict. It doesn't detail overwrite behavior or permissions.

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?

One sentence, efficient and front-loaded. No wasted words, but could benefit from more structuring.

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?

Despite having an output schema, the description is under-specified for a mutation tool. It doesn't mention overwrite behavior, error cases, or how the path should be specified. Limited compared to sibling tools.

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 0%, so description should compensate. The description only mentions base64 data and size limit, but does not explain 'path', 'overwrite', or 'content_base64' semantics. The title mentions base64, but the description is thin.

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 uploads a file from base64 data, and distinguishes from siblings like download_file_base64 and write_text_file. However, it doesn't mention the specific resource (Nextcloud) explicitly, though the title does.

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 mentions 'small binary file' and 'transfer size limit', indicating when to use but not explicitly when not to use or alternatives. No sibling differentiation or exclusions.

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