clm_user_setting_command_update_user_favorite_material

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

Annotations already declare idempotentHint=true and destructiveHint=false, covering the safety profile. The description adds value by disclosing the bidirectional toggle behavior (add vs. remove driven by a flag) and the 'current user' scoping, which are not present in the annotations. No contradiction with annotations exists.

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?

A single tight sentence with a front-loaded verb and no filler. Every clause carries meaning: action, resource, ownership (current user), and scope (site).

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?

For a simple toggle tool with an output schema and safety annotations present, the description adequately covers purpose and scope. The only meaningful gap is the explicit IsFavourite true/false mapping, which is absent from both the schema and the description.

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 description coverage is 0%, so SiteId, MaterialId, and IsFavourite are undocumented in the schema itself. The description partially compensates by mapping 'site' to SiteId, 'material' to MaterialId, and implying the toggle role of IsFavourite, but it never explicitly states that IsFavourite=true adds and IsFavourite=false removes.

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 states a specific action pair ('adds or removes') applied to a clear resource ('material from the current user's favorite materials list') with explicit scoping ('for a given site'). It clearly distinguishes this tool from the other user_setting sibling commands, which concern cockpit equipment filters and weekly filters rather than favorites.

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?

No explicit when-to-use or when-not-to-use guidance is provided, and no alternative tool is named. Usage is reasonably implied by the resource naming and the user_setting_* command family, but the description would earn a higher score if it stated when this tool should be selected over the filter-related user setting commands.

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