Write Nextcloud text file

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

The description adds useful behavioral context beyond the annotations: existing files are protected by default and only overwritten when overwrite is explicitly true. This clarifies the destructiveHint=true annotation by specifying the exact condition under which destruction occurs.

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 two short sentences with no filler. The main action is front-loaded, and the critical overwrite safeguard is stated separately and clearly.

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 simple three-parameter write tool with an output schema and annotations, the description is largely sufficient. It covers the key safety behavior (overwrite protection) and encoding, though it does not mention path conventions or failure behavior when an existing file is not overwritten.

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?

With 0% schema description coverage, the description must compensate for parameter meaning. It clarifies the overwrite parameter ('unless overwrite is explicitly true') and content type (UTF-8), but does not explain path semantics or required path format, leaving some gap.

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 a specific verb and resource: 'Write a UTF-8 text file.' It clearly identifies the tool's core action and distinguishes it from sibling tools like read_text_file or upload_file_base64 by emphasizing UTF-8 text content.

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?

There is no guidance on when to use this tool versus alternatives such as upload_file_base64 or create_folder. The description states what the tool does but does not provide use cases, exclusions, or references to sibling tools.

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