Set Skills (Replace All)

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

Description reinforces annotations (destructiveHint=true) by stating 'Destructive: this overwrites all existing skills' and 'Any current skill not in the list is removed.' Adds context about account parameter usage and correct return behavior.

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?

Description is well-structured: core purpose first, then Args section, Returns, warning, and usage examples. Every sentence adds value without redundancy.

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, but 'Returns: confirmation' is sufficient for a mutation tool. With detailed annotations, clear parameter descriptions, and alternative suggestions, the description is fully complete for an agent.

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%, but description adds meaning: skills are 'complete set of skill names or numeric IDs' and account parameter clarifies 'see freelancer_list_accounts for labels'. This aids agent understanding beyond 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?

The title 'Set Skills (Replace All)' and description 'Replace your ENTIRE skill list' clearly state the verb (replace) and resource (skill list). It distinguishes from siblings like freelancer_add_skills (append) and freelancer_remove_skills (remove specific).

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 suggests 'Consider freelancer_list_skills first, and freelancer_add_skills if you only want to append.' Also provides example use cases ('Set my skills to exactly Python, n8n and React', 'Replace all my skills with this list') and warns about destructive nature.

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