set_fx_preferences

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

Discloses file paths for storage and that it overrides per-category. No annotations, so description carries burden. Could mention overwrite behavior or error handling, but covers key aspects.

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?

Starts with one-line summary, then file paths, then structured Args section with example. No unnecessary words; every sentence adds value.

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?

Covers purpose, parameters, storage location, and usage hint. Lacks details on return value or error messages, but adequate for a simple save operation without output schema.

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 has 0% description coverage; description adds full meaning: JSON object mapping categories to plugin names, with example and valid categories list. Greatly enhances schema.

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 'Save user FX preferences — per-category plugin overrides.' Specific verb and resource, and distinguishes from siblings (no other tool does this).

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?

Provides context: mix pipelines consult it before auto-picking. Includes important note to check plugin names with fx_list_installed. Lacks explicit when not to use or alternatives.

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