Update Preferences

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

Discloses that changes persist, immediately refilter feeds/recommendations/alerts, and returns the full updated preference set. No contradiction with annotations (idempotentHint=true, destructiveHint=false).

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?

Efficiently structured: starts with verb, covers all key aspects in a few sentences, no redundant 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?

Covers all important behavioral implications (persistence, feed effects, return value) despite no output schema. 6 parameters are well explained in schema and description.

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 provides full descriptions for all 6 parameters. Description adds context (e.g., 'bottom of a job's listed range must clear it' for min_salary_usd). Exceeds baseline by clarifying semantics.

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 it updates the authenticated user's matching preferences, lists specific fields, and distinguishes from sibling tools (e.g., search_jobs, get_profile).

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?

Provides explicit example queries ('raise my minimum salary to $150K') and notes the effect mirrors editing Settings on the website. Does not explicitly state when not to use, but the context is unambiguous.

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