List My Skills

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the description adds value by specifying the return structure (numeric ID, name, category). No contradictions exist, and the behavior is well-disclosed.

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?

The description is concise—four lines covering purpose, return fields, arguments, and usage examples—with no unnecessary words. Information is front-loaded and well-structured.

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?

Despite no output schema, the description explicitly states what is returned (ID, name, category), which is sufficient for a list tool. The sole optional parameter is fully documented, and the use-case examples complete the contextual picture.

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% for the single optional parameter 'account', and the description repeats the schema's explanation about using freelancer_list_accounts for labels. While the cross-reference is helpful, the description doesn't add significant new meaning beyond the schema, so a baseline 3 is appropriate.

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 'List My Skills' and description 'List the skills (jobs) currently on your own Freelancer.com profile' use a specific verb (list) and resource (skills on own profile), clearly distinguishing it from sibling tools like freelancer_search_skills (search all skills) and freelancer_set_skills (modify).

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 'Use when:' section provides concrete example queries, giving clear context for when to invoke the tool. It also cross-references freelancer_list_accounts for the account parameter. While it doesn't explicitly state when not to use or list alternative tools, the examples are sufficient 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.