Upload Nextcloud file from base64

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

Annotations already flag destructiveHint=true and readOnlyHint=false, and the description adds real value on top: strict base64 enforcement, size limits, the overwrite precondition, and the no-public-sharing restriction. It doesn't quantify 'small' or state what error occurs on failure, which keeps it below a 5.

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?

Three short sentences, with the core write action and scope front-loaded before the constraints. The fragments 'no public sharing' and the trailing clause are slightly terse/telegraphic but every sentence carries information.

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?

An output schema exists, so return values need not be explained, and the description covers the key safety and precondition facts. The remaining gaps (the actual size limit behind 'small', path format) are minor but non-trivial for a zero-coverage schema.

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 0%, so the description carries the full burden and does touch all three params – path (workspace root), content_base64 (strict base64), overwrite (required for existing files). However it never specifies path format, whether it's relative to the root, or the actual size cap, leaving meaningful gaps.

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?

States a specific verb (write) and resource (small binary file) plus a clear scope limit (private Nextcloud workspace root). This implicitly separates it from write_text_file and download_file_base64, though it never names the siblings explicitly, so an agent must infer the division of labor from the type keywords.

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?

It gives one actionable rule – existing files require overwrite=true – and a constraint (no public sharing). But there is no explicit when-to-use versus the closely related write_text_file or create_folder, so the routing decision is only implied by 'binary' and 'workspace root'.

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