Remove Skills

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

Beyond annotations, it warns '⚠️ This modifies your real profile.' and mentions return value as confirmation. Annotations already indicate destructive and idempotent hints, so description adds useful context.

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?

Well-structured with clear sections: purpose, args, returns, warning, and usage examples. Every sentence serves a purpose, no fluff.

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 essential aspects: what it does, parameters, warning about modification, return value, and usage examples. No output schema needed as return is simple confirmation.

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%, so baseline is 3. Description explains the skills parameter can be names or numeric IDs (already in schema) and clarifies the account parameter references freelancer_list_accounts, adding value.

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 the verb 'remove' and the resource 'skills from your Freelancer.com profile'. Distinguishes from sibling tools like freelancer_add_skills and freelancer_set_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 when:' examples, but does not differentiate from alternatives like adding or setting skills. Nonetheless, the examples are helpful for typical use cases.

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