get_user_preferences

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

With no annotations, the description carries the burden of disclosing behavior. It clearly indicates a read-only operation via 'Retrieve' and clarifies the optional key behavior, but it does not mention return format, error handling, or what happens if a key is not found. These gaps are minor for a simple getter but leave some 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?

The description is two sentences, front-loaded with the action, and every sentence earns its place. It is appropriately sized for the tool's simplicity with no fluff or redundancy.

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?

Given the tool has only one optional parameter and no output schema, the description adequately explains the core functionality and even gives a practical use case ('see what locations the user has saved'). It does not detail the return structure, but for a simple preferences getter this is not a significant omission.

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 100%, so the schema already explains the 'key' parameter well. The description merely restates what the schema says ('get a specific preference by key' and 'If omitted, returns all preferences') without adding extra meaning like examples or default behavior.

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 states a specific verb 'Retrieve' with a clear resource 'user preferences', and explains both modes: all preferences or a specific key. This clearly distinguishes it from sibling tools like get_weather_forecast or set_user_preference.

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 a concrete use case: 'Use this to see what locations the user has saved.' It does not explicitly exclude alternatives or mention when to use set_user_preference instead, but the context is clear enough for a simple getter.

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