zotero_set_setting

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

No annotations are provided, so the description carries the full burden. It does disclose an important behavior: 'Overwrites the previous value.' However, it does not explain what happens if the setting does not exist, whether authorization is required, or whether the change is reversible. The disclosure is partial but meaningful.

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. It front-loads the operation, clarifies the resource scope, provides a representative use case, and states the overwrite behavior. Every sentence earns its place.

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 two-parameter tool with a complete schema and an output schema, this description is largely sufficient. It identifies the resource, the effect, and an example. It could be more complete by mentioning how to discover valid settings or whether overwriting is the only side effect, but no critical information seems missing for basic use.

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% and both parameters have descriptions, so the baseline is 3. The description adds extra meaning by explaining that 'setting' is a key under /settings and by giving a concrete example, which helps the agent understand what kind of value is expected beyond the raw schema.

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: 'Set one library setting' and clarifies it is 'a key under /settings'. The example 'syncing metadata used by plugins' makes the purpose concrete, and it is clearly distinguishable from sibling tools like zotero_list_settings and zotero_update_item_fields.

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 gives some context for when this tool is relevant via the plugin-metadata example, but it does not explicitly state when to use this tool versus alternatives, nor does it mention zotero_list_settings as the way to inspect existing settings. Usage guidance is implied rather than explicit.

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