manage_preferences

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

Matches annotation (not read-only). Adds context that it's local and requires no API key, which is useful safety info. Does not detail effects of updates or persistence.

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?

Two sentences, front-loaded with core purpose, then helpful context. Every word earns its place.

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 7 params, no output schema, and annotations not read-only, description provides reasonable overview but lacks detail on actions, parameter specifics, and return values.

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 coverage, description only mentions high-level fields but doesn't explain each parameter's purpose or constraints. Action enum values not clarified. Partial but insufficient.

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 the tool reads/updates local preferences and lists specific fields (style, model, aspect ratio, etc.). Distinct from sibling tools which are generation-oriented.

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?

Tells when to use (for preferences) and mentions it's free/local, but lacks explicit exclusions or alternatives. Adequate but not strong.

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