set_user_skills

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

With no annotations, the description carries full responsibility for behavioral disclosure. It only says 'Set or overwrite' and does not clarify whether omitted fields (avoidTags, scopePreferences) are cleared, whether it merges with existing skills or fully replaces them, or any side effects. This ambiguity is significant for a mutation tool.

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 sentence with the action verb and resource front-loaded. No filler words, and it conveys the core operation efficiently.

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 tool with no annotations and no output schema, this description is too sparse. It fails to explain overwrite semantics (full replacement vs. merge), the fate of optional fields, or the expected result. In the context of sibling skill-management tools, this is insufficient for correct selection and invocation.

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?

The schema provides 100% coverage for all three parameters with descriptions and enum values. The description adds little beyond naming 'scope preferences', but the baseline of 3 applies because the schema already documents parameters effectively.

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 uses a specific verb phrase 'Set or overwrite' and names the resource 'user skill tags and scope preferences'. This clearly differentiates from sibling tools like add_user_skills (additive) and clear_user_skills (removal) by implying replacement semantics.

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 word 'overwrite' implies this should be used when replacing existing skill tags, but the description does not explicitly state when to prefer this over add_user_skills or remove_user_skill. It provides implied usage context without explicit alternatives or exclusions.

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