Add Skills

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

Discloses that the tool modifies the real profile and mentions the Freelancer-imposed maximum skills limit. Annotations (idempotentHint=true) are not contradicted; the description adds useful behavioral context beyond annotations.

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?

Efficiently structured with clear sections (Args, Returns, warning, usage). Every sentence adds value, no fluff. Properly front-loaded with the main action.

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?

Given the complexity (profile modification, multiple accounts) and absence of output schema, the description covers all essential aspects: functionality, parameters, warnings, and usage clues. It also differentiates from sibling tools adequately.

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?

Adds meaningful details beyond the schema: explains that skills can be names or numeric IDs, names are resolved via the catalogue, and account is optional with a reference to freelancer_list_accounts. Schema coverage is 100%, but the description enriches understanding.

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 it adds skills to Freelancer.com profile while preserving existing ones. Differentiated from siblings like freelancer_set_skills and freelancer_remove_skills by explicitly mentioning 'keeping your existing skills'.

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 explicit use examples for the agent (e.g., 'Add n8n and Zapier to my skills'). Implicitly contrasts with freelancer_set_skills by noting skills are added, not replaced. Could explicitly state when not to use it, but the examples and sibling list make it clear.

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