config_set

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

Warns that incorrect values can break Nextcloud, indicating potential destructiveness. But with no annotations, it lacks details on authentication, side effects, or error states, leaving some behavioral ambiguity.

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?

Two concise sentences: first states purpose, second adds critical warning. No wasted words, front-loaded.

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 5 parameters and no schema descriptions, the description omits parameter explanations and output format. The warning is helpful but insufficient for a potentially destructive tool with many options.

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 coverage, the description should explain parameters but only hints at 'scope' via 'system or per-app'. Does not clarify 'key', 'value', 'app_name', or 'value_type' meaning or formatting.

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?

Clearly states the tool writes config values, distinguishing system vs per-app scope. The warning to prefer config_get before changing also differentiates it from the sibling config_get.

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?

Explicitly advises using config_get before writing to avoid breaking Nextcloud, providing clear usage context. However, it does not mention non-usage scenarios or prerequisites.

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