manage_preferences

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

Annotations indicate readOnlyHint=false, and description says 'read or update', aligning with mutation capability. However, no details on persistence, error behavior, or side effects beyond what annotations imply.

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: first defines scope, second gives a concrete usage tip. No filler or redundancy, extremely efficient.

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?

No output schema or return format described; missing details on what 'get' returns. For a tool with 8 parameters and 4 actions, more behavioral context (e.g., persistence, error cases) would improve completeness.

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 coverage is 100% with descriptions, but the description adds context by listing the fields and suggesting a use case (get at start). This enhances understanding beyond the schema alone.

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?

Description clearly states the tool reads or updates user preferences, listing specific fields like default style, aspect ratio, and model. It distinguishes from sibling tools (e.g., generate_image, search_gallery) which focus on generation or searching, not user settings.

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?

Explicitly recommends calling with action 'get' at conversation start to load preferences, but lacks guidance for other actions (set, add_favorite, remove_favorite) and when not to use this tool. Sibling uniqueness partially compensates.

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