users_prefs_set

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

With no annotations, the description carries full responsibility for behavioral disclosure. It confirms mutation ('Set') but omits details on permissions, side effects, reversibility, or what happens to existing preferences. The 'legacy undocumented' tag adds a warning but no actionable context.

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 extremely concise at one sentence, but this comes at the cost of omitting essential details. While it avoids fluff, the brevity undermines its usefulness for an agent.

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 (not detailed in context) and low complexity, the description fails to provide complete context. It lacks information on return values, error conditions, or how the preference names map to known settings. The 'legacy undocumented' label hints at risks but does not mitigate the incompleteness.

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%, yet the description adds no information about the two parameters (name, value). It does not explain what values are valid, or any constraints beyond the schema's basic strings. This is a critical 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 clearly states the tool sets a user preference, which is a specific verb-resource pair. The sibling tools include users_prefs_get, so the purpose is distinct from its get counterpart. However, the phrase 'legacy undocumented' may cause uncertainty about when to use it.

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?

No usage guidelines are provided. The description does not indicate when to use this tool vs. alternatives like users_profile_set, nor does it specify prerequisites or exclusions. The 'legacy undocumented' note hints at deprecation but offers no substitute.

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