manage_preferences

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

The description correctly indicates both read and update operations, matching the annotation readOnlyHint: false. It adds context by listing the preference fields and suggesting initial use of 'get', which is helpful beyond the annotation alone.

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-loading the core purpose and a key usage tip. Every word earns its place 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's complexity (8 params, 4 actions) and no output schema, the description provides a high-level overview that, combined with the detailed schema, is sufficient. Could be slightly more explicit about what each action does, but overall adequate.

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 100% schema description coverage, the baseline is 3. The description lists the fields but doesn't add significant meaning beyond what the schema already provides for each parameter. Minor value from the 'get at start' hint.

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 reads or updates user preferences and lists the specific fields (style, aspect ratio, model, style notes, favorite prompts). It distinguishes itself from sibling tools (all generation-focused) as a preference management tool.

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 explicitly recommends calling with action 'get' at conversation start to load preferences, providing a clear usage pattern. It doesn't mention when not to use or alternatives, but the sibling tools are unrelated so no exclusions are needed.

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