manage_preferences

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

Annotations indicate readOnlyHint=false, and the description clarifies it supports both reading and updating, which adds context. However, it does not disclose behavioral traits such as whether changes are persisted immediately, require additional steps, or affect other operations.

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, concisely stating the purpose and key attributes (free, local, no API key). Every word adds value with no 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 7 parameters, no output schema, and no parameter descriptions, the description is insufficient for an agent to effectively invoke the tool. It lacks details on parameter value ranges, required combinations, and expected behavior for each action.

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 description coverage, the description must compensate but only lists parameter names without explaining valid values, formats, or constraints. For example, 'style' and 'resolution' are mentioned but not what values they accept, leaving agents to guess.

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 explicitly states the tool's purpose: to read or update local LemGen preferences. It lists the specific preference fields (style, model, aspect ratio, resolution, favorite prompt ids), clearly indicating the resource and actions.

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 implies usage for managing preferences but lacks explicit guidance on when to use this tool versus alternatives. No exclusions or when-not-to-use scenarios are mentioned, and sibling tools like 'prompt_tools' or 'list_models' are not differentiated.

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